si addsubproject
adds an existing subproject to a project
Synopsis
si addsubproject [-r subproject revision|--subprojectRevision=subproject revision] [--subprojectDevelopmentPath=subproject development path name|--variant=subproject development path name] [--type=[normal|variant|build|default]] [(-Pproject|--project=project)] [(-S sandbox|--sandbox=sandbox)] [--[no]failOnAmbiguousProject] [--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]] [--cpid=ID|--changePackageId=ID] [--[no|confirm]closeCP] [--issueId=value] subproject location...
Description
si addsubproject allows you to re-add a dropped subproject. For example,
si addsubproject c:/Aurora_Program/bin/Libra/project.pj
|
|
If you want to add a normal subproject to a variant project, the normal subproject does not require a development path.
|
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 checkpoint 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|default]
specifies the new configuration type for the subproject.
--type=normal configures the subproject based upon the current state of the subproject.
--type=variantconfigures the subproject based upon a specific development path. The option is used with --variant=subproject development path name or --subprojectDevelopmentPath=subproject development path name.
--type=buildconfigures the subproject as a static subproject based upon a specific checkpoint of the master project that is used for building or testing the project, but not for further development. This option is used with -r subproject revision or --subprojectRevision=subproject revision.
--type=default configures the subproject based on the type that is consistent with the parent project that you are adding the subproject to. For example, if you add a subproject to a normal project, the subproject is added as a normal type. For information on what the default type is, see your administrator.
• --cpid=ID
• --changePackageId=ID
identifies a change package that is notified of this action, for example, 1452:1. Note the following about using this option:
• This option can only be specified if change packages are enabled.
• If the integration is enabled, but it is not mandatory to specify a change package, or if no change package is applicable, you can specify --changePackageId=:none.
• The next time you are prompted for a change package ID, the last used change package ID is displayed by default, if :none was specified or at least one change package was successfully updated from the last operation.
• --[no|confirm]closeCP
closes the change package after command completion.
• --issueId=value
specifies the issue ID that corresponds to the change package that records the changes.
• subproject location...
specifies the path and name of the subproject you want to add, for example, c:/Aurora_Program/bin/Libra/project.pj
Diagnostics
See the
diagnostics reference page for possible exit status values.
Preferences
Using
si setprefs or
si viewprefs, you are able to set or view the preference keys for this command.
See Also
• Commands:
si checkpoint,
si configuresubproject,
si createproject,
si createsubproject,
si addsubproject,
si movesubproject,
si createsandbox,
si drop,
si dropproject,
si projectinfo,
si projects,
si sharesubproject,
si viewproject
