si sharesubproject
shares an existing subproject between multiple projects
Synopsis
si sharesubproject [--sharedProject=project location] [--[no]preserveCase] [-r subproject revision|--subprojectRevision=subproject revision] [--subprojectDevelopmentPath=subproject development path name|--variant=subproject development path name] [--type=[normal|variant|build|default]] [--[no|confirm]closeCP] [--cpid|--changePackageId=ID] [--issueID=value] [(-P project|--project=project)] [(-S sandbox|--sandbox=sandbox)] [--[no]failOnAmbiguousProject] [--devpath=development path name] [--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 location
Description
A shared subproject is a subproject that is a member of more than one project. Integrity Lifecycle Manager allows you to share a subproject between two or more projects by referencing the original subproject. A shared subproject allows you to access common members across many projects. Shared subprojects are not required to be located within the same directory structure or project hierarchy.
A shared subproject functions the same as an unshared subproject and is accessible by the same commands.
Shared subprojects that were created in a previous version of Integrity Lifecycle Manager (formerly MKS Source or Source Integrity Lifecycle Manager Standard Edition) are detected as they are accessed by Integrity Lifecycle Manager without disrupting the operation. The format of these subprojects is retained until you change or update it to the new format by re-configuring it.
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.
• --sharedProject=project location
specifies the path and name of the subproject you want to share. For details on how to specify a project, see the
-P option on the the
options reference page.
• --[no]preserveCase
uses the same case that exists on the file system when specifying a destination directory in a Sandbox. By default, the destination directory uses the same case.
• --[no|confirm]closeCP
closes the change package after command completion.
• -rsubproject revision
• --subprojectRevision=subproject revision
• specifies the checkpoint number (for build subprojects). For example, 1.5. This option is used with --type=build.
|
|
This option cannot be used if you specify a project using a keyword string for the --sharedProject option. This option is also mutually exclusive with the --subprojectDevelopmentPath or --variant options.
|
• --subprojectDevelopmentPath=subproject development path name
• --variant=subproject development path name
identifies the development path of a variant subproject. This is a label that was associated with a branch of the subproject by
si createdevpath. Paths that include spaces must be enclosed by quotes. The following characters may not be used in a development path: \n, \r, \t, :, [', '], #. This option is used with
--type=
variant
|
|
This option cannot be used if you specify a project using a keyword string for the --sharedProject option. It is also mutually exclusive with the --subprojectRevision option.
|
• --type=[normal|variant|build|default]
specifies the new configuration type for the subproject. If you specify the --sharedProject option using a flat string, by default the subproject type is the same as the parent project type. If you specify the --sharedProject option using a keyword-based string, by default the subproject type is determined by the specified configuration. Use this option to specify a configuration type other than the default.
--type=normal configures the subproject to the master (non-variant) version of the subproject.
--type=variant configures 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=build configures 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 to be the same as 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.
• subproject location
specifies where in the project you want the shared subproject to appear, for example, c:/Aurora_Program/bin/Libra/.
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 addsubproject,
si checkpoint,
si configuresubproject,
si createproject,
si createsandbox,
si createsubproject,
si movesubproject,
si drop,
si dropproject,
si projectinfo,
si projects,
si viewproject
