Rational Developer for System z


Adding an Eclipse project to an SCLM project

This scenario describes how to add the contents of an Eclipse project shown in the Package Explorer to an existing SCLM project.

The project SCLMHTTPConnector is a J2EE project that contains the SCLM Developer Toolkit HTTP connector source. It contains approximately 11 files, consisting of Java source, various property and XML files. The following figure shows the project mapped to an SCLM project called SCLMDW. This file list indicates that these files are not currently under SCLM control with the Not In SCLM decorator.

Figure 1. SCLMHTTPConnector project
SCLM HTTP Connector project
To add an Eclipse project to an SCLM project, do the following:
  1. Select your project from the Eclipse Navigator, right click and select Team->Add to SCLM.

    The Resource Selection Page is displayed listing all the files in the project.

  2. Select the files you want imported into SCLM by selecting the check box next to the folder or file. The list also indicates which files are not currently in SCLM.

    It is important for project organization that the correct type and language are assigned to the members. This can be automated by setting type and language in the SCLM Preference Page File Types. To set the default type and language for members, select Window->Preferences->Team->SCLM Preferences->File Types.

  3. If all the files selected have a Type and Language associated with them, click Finish to complete the function.
  4. Click Next to display the full list of members with the associated language and type. If a member does not have an associated language and type, select member and click Update Selected... to associate a Type and Language with that member. In this case, all Java source is stored as type CSOURCE with a language of Java. All other files are saved as type CSOURCE and language J2EEPART.
  5. Select Enable Forced Migrate option to copy the IDE files over current SCLM members of that name. This function should be used with care.
  6. Click Next and associate an ARCHDEF with the project you are importing by selecting the Include ARCHDEF statements check box. Specify the name of the architecture definition that will be created or updated to contain the names and types of the members being added to SCLM. This allows any subsequent build functions to reference the file and obtain the list of members to be built.
  7. If this is a Java/J2EE project, you can generate the Ant build script required to build the project. To generate this script, click Generate Build Script. The dialog presented allows you to enter the type of J2EE project plus additional options to add the Java source to the archive file. Click Finish to continue. The ARCHDEF and build script are created, and all of the source code is transferred and stored in SCLM.

    When the function has completed a return code dialog displays the results of the migration.

    Note: If the file already exists in SCLM, this function will fail unless you check the Enable Forced Migration option. The preferred method is to rename the IDE file or import that member into the Package Explorer so that the project is in sync with SCLM. If you copy the contents of that file into a temporary area before importing and pasting that code in, you can use the Compare with Latest From SCLM function to show the difference between the files.

    The project navigator now shows a project with the files migrated into SCLM. File names are no longer displayed with a [Not in SCLM] indicator. SCLM functions are available for the files from the Team menu. Services such as check-out, check-in, etc. are now enabled for these files.


Terms of use | Feedback



This information center is powered by Eclipse technology. (http://www.eclipse.org)