Projects must be placed under MKS version control, which requires an MKS Integrity project and Sandbox. Using the Team Support approach, you can work through a wizard that creates the MKS Integrity projects and Sandboxes, and adds existing project files as members.
IMPORTANT When you create an MKS Integrity project and Sandbox, the project can
reside anywhere on the MKS Integrity Server, but the Sandbox must reside in the same directory as the Eclipse project.
Once an Eclipse project is under MKS version control, you can perform MKS Integrity operations, such as checking in files and checkpointing projects.
To create an MKS configuration management project and Sandbox in your workspace 1 In your workspace, select the Eclipse project you want to place under MKS version
control.
2 Right click and select Team > Share Project. The Share Project panel displays. 3 Select MKS as the repository type.
4 Click Next. The MKS Sharing Wizard displays. 5 Select one of the following options:
Activate the integration for an existing MKS Source Sandbox initiates MKS Integrity and opens the Sandbox you previously created in your workspace. This option is selected by default. If a Sandbox does not exist, this option is disabled.
Create a new Sandbox for an existing MKS Source project creates a new Sandbox for an existing MKS Integrity project under MKS version control. If you select this option, you are prompted to choose an MKS Integrity project and, optionally, a development path.
Create a new MKS Source project and Sandbox creates a new MKS Integrity project accessible to all users and a Sandbox in your Eclipse workspace.
6 By default, the option for Add all files when creating the new MKS Source project is enabled. You can disable this option if you want to manually add each file in your project to MKS version control.
This option is only available if you selected the Create a new MKS Source project and Sandbox option in step 5.
7 Click Next. The options for creating an MKS Integrity project display. 8 For the option you selected in step 5, choose one of the available options:
Create a new top-level MKS Source project and click Finish. The Specify Project dialog box displays. In the File name field, specify the name of the project you want to create on the MKS Integrity Server.
Create a new subproject of an existing MKS Source project and click Next. Choose the project to create the subproject against. Optionally, you can select one of the project’s development path. To create the subproject, click Finish.
9 If your project contains files and you are using change packages, you are prompted to specify a change package to associate with the files. Select an existing change package, or click Create to create a new change package, then click OK.
If you are not using change packages, proceed to the next step. The Create Archive dialog box displays.
10 Modify the Create Archive options.
NOTE If MKS Integrity finds an existing archive, the Existing archive detected
dialog displays.
MKS Integrity automatically creates a Sandbox with the project name in your Eclipse workspace.
11 If your project contains files and you associated them with a change package, you must commit them to the MKS repository by submitting the change package associated with the files via the Synchronize view. For more information, see “Team Synchronizing” on page 54. If your project contains file and you are not using change packages, submit the changes by selecting MKS > Submit Changes. For more information, see “MKS Integrity Commands” on page 46.
To import a project from MKS Integrity
If you want to start using an existing MKS project, you can import it to create a Sandbox in your workspace.
NOTE This is the only method of sharing a project that allows you to rename the project in your workspace. This enables you to import multiple versions of the same project.
1 In your workspace, select File > Import. The Select panel of the Import wizard displays. 2 Under MKS, select Projects from MKS.
3 Click Next. The Choose the MKS project to import panel displays.
4 Select the project to import. All Eclipse projects currently under MKS version control are listed.You can use the Filter field to filter the projects by name.
NOTE If an Eclipse project is missing from this list, it means that the project descriptor file (.project file) has not been put under MKS version control.
5 Specify the configuration of the project to import. If importing a variant project, specify the Development Path Name where the project is located. If importing a build project, specify the Revision number or Label applied to the project.
NOTE If you are importing a variant or build configuration of a project that you already have in your workspace, you must edit the project name in the Project Name
field since you cannot have two projects with the same name in the same workspace.
6 Specify the location to import the project to. This can either be the default workspace location or a location specified by you.
In either case, the projects are placed in:
selectedLocation/projectName
where projectName is the name of the project as specified in the Project Name field. NOTE The relative paths of imported projects are not maintained.
7 Edit the Project Name if required.
NOTE
If there are dependencies between projects, renaming the project will result in
compile errors.
The name in the .project file is not changed when you edit the project name in this field.
8 Click Finish.
A directory is created for the project in the specified location, a Sandbox is created within that directory and the Eclipse project files are added.
Importing an MKS Integrity project results in an identical Eclipse project structure and information within your workspace.
NOTE The Import wizard is only available if the Eclipse integration is connected to an MKS Integrity Server that uses the database repository option. If the integration is connected to a server that uses the RCS-style repository option, the Import wizard is not available and an error message displays when attempting to the run the wizard.