Description - Mks.com

si configuresubproject
configures a subproject's type
SYNOPSIS
si configuresubproject [-r subproject revision|--subprojectRevision=subproject revision]
[--subprojectDevelopmentPath=subproject development path name|--variant=subproject development path
name] [--type=[normal|variant|build|reset]] [(-P project|--project=project)]
[(-S sandbox|--sandbox=sandbox)] [--devpath=path] [--hostname=server] [--port=number]
[--password=password] [--user=name] [(-?|--usage)] [(-F file|--selectionFile=file)] [(-N|--no)]
[(-Y|--yes)] [--[no]batch] [--cwd=directory] [--forceConfirm=[yes|no]] [(-g|--gui)] [--quiet]
[--settingsUI=[gui|default]] [--status=[none|gui|default]] subproject or subsandbox
DESCRIPTION
Once you have created or added a subproject, you can modify the type to suit your needs. For example, you can
change a normal subproject to a build subproject to suspend development, or you can change a variant subproject to
a normal subproject to continue development on the main trunk.
Important: Any changes you make when reconfiguring a subproject affects the project as a whole and any shared
subprojects. More specifically, changing the type, revision, or development path of a subproject can radically change
the list of members of that subproject. After configuring a subproject, existing sandboxes whose contents were in
sync with the subproject before it was configured will display deltas when you use si viewproject and si
viewsandbox, reflecting the following possible differences:
● Members that exist in both the old and new version of the subproject display a delta if the working revision in
the sandbox is different from the new member revision.
● Members that are in the new version of the subproject but were not in the old version of the subproject display
a "no working file" delta, indicating that the sandbox does not have a copy of the new member yet.
● Members that were in the old version of the subproject but are not in the new version display as former
members.
● Subprojects that were in the old version of the subproject but are not in the new version will display as former
subprojects.
Options
This command takes the universal options available to all si commands, as well as some general options. See the
options reference page for descriptions.
-r=subproject revision
--subprojectRevision=subproject revision
specifies the revision number (for build subprojects). For example, 1.5. This option is used with -type=build.
--subprojectDevelopmentPath=subproject development path name
--variant=subproject development path name
specifies the development path name (for variant subprojects). For example, Service_Pack3. This option is
used with --type=variant
--type=[normal|variant|build|reset]
specifies the new configuration type for the subproject.
74 of 457