User Guide - Mks.com

Dropping a
Subproject
Working With Subprojects
Build configures a static subproject based upon a specific revision
of the master project that is used for building or testing the
project, but not for further development.
To specify a revision to base the build project, do one of the
following:
Select Revision, and from the list select a project revision
number.
Select Label, and from the list select a project label.
Reset to default value configures a subproject to the parent project
type.
4 Click OK to complete the operation.
The subproject is re-configured.
Subprojects configured as a build subproject appear with a build
project icon (Project view: or Sandbox view: ), and the revision
or label that the build project is based on, for example, tools.pj
(1.1).
Subprojects configured as a variant subproject appear with a variant
project icon (Project view: or Sandbox view: ), and the
development path that the variant project is based on, for example,
tools.pj (release_1).
Subprojects configured as a normal subproject appear with the
standard project and sandbox icons.
Depending on what the default project type is, subprojects configured
as default projects, may or may not appear with a different icon.
If a subproject has outlived its usefulness or just does not belong in a
project anymore, you can remove it at any time. You can remove a
subproject through a Project view or through a Sandbox view. For more
details on removing a subproject through a Sandbox view, see “Dropping
Members From a Project” on page 172.
After you remove a subproject from a project, it is no longer listed as part
of the sandbox or master project, but the subproject’s history remains in the
project record, in case you need to recreate an earlier version of the project.
IMPORTANT
When you remove a subproject, you also remove all members within that
subproject.
133