Checking Classes Out from an SCM Repository (Windows)

In the IDE, you can select classes and interfaces that you wish to check out of an external SCM tool's repository. When you take this action, VisualAge for Java automatically does the following things:

You can select classes and interfaces individually, or you can select them grouped in projects or packages as input to the SCM tool. There is no other relationship between projects and packages in VisualAge for Java and the organizational constructs used by your SCM tool.

Before you can check classes in or out, you must add them to source control in your SCM tools' repository. See the list of topics below for links to related information.

To check classes and interfaces out of your SCM tool's repository:

  1. From the Workbench window, select the classes and interfaces that you wish to check out, or select the projects or packages that contain the classes you wish to check out.
  2. From the pop-up menu, select Tools > External SCM > Checkout. VisualAge for Java will pass the list of classes and interfaces to the SCM tool, which validates the request.
  3. If there are no problems, the Set Comments dialog box will appear. Enter the comments that you want the SCM tool to log when it checks the classes out of its repository, and click OK.

The classes and interfaces are checked out of the SCM repository, from the project that you identified when you set your SCM connection parameters. Open editions of the classes and interfaces are created in the VisualAge for Java repository, and added to your workspace. The classes and interfaces remain checked out of the SCM repository until you check them in again, or until you undo the checkout operation.

tentergf.gif (577 bytes) Since the class already existed in VisualAge for Java, the owner of the new edition is the existing class owner. As the person who created the open edition, you are the class developer and therefore the only person who can version that particular edition.

tentergf.gif (577 bytes) If you check out classes and interfaces from the SCM repository, and if the containing package or project in your VisualAge for Java workspace has been versioned, then a scratch edition of the package or project will be created. To prevent this, create an open edition of each project or package before selecting its classes for checkout.

Checking Out Classes that Were Not Developed in VisualAge for Java
The above procedure requires that the classes or interfaces are already in your workspace, and therefore in the VisualAge for Java source code repository. To check out classes that exist in the SCM repository but not in the VisualAge for Java repository:

  1. Start the native client software for your SCM tool by selecting Tools > External SCM > Launch SCM Program from the pop-up menu of any program element in the workspace.
  2. Use the SCM client to check the classes out.
  3. From the Workbench window, select File > Import to import the files into the VisualAge for Java repository. Open editions of the classes and interfaces will be created in the workspace.
  4. tentergf.gif (577 bytes) To change ownership of the classes to the team member who will be responsible for them, select Manage > Change Owner.

ngrelc.gif (533 bytes)
External SCM Tools (Windows)
Workspace
Editions and Versioning

ngrelt.gif (466 bytes)
Preparing to Use an External SCM Tool (Windows)
Setting Your SCM Connection Parameters (Windows)
Adding Classes to the SCM Repository (Windows)
Checking Classes In with an External SCM Tool (Windows)
Undoing Checkout with an External SCM Tool (Windows)
Getting the Latest Version from an External SCM Tool (Windows)
Comparing a Class to a Version in the SCM Repository (Windows)
Displaying SCM History (Windows)
Launching Your SCM Program (Windows)
Importing Files from the File System