The interface to external SCM tools allows you to import the most recently checked-in editions of classes and interfaces from your SCM repository into VisualAge for Java, without checking them out. You might do this for testing purposes.
As with checkout, VisualAge for Java will do the following things when you get the latest classes and interfaces from your SCM library:
To get the most recently checked-in editions of classes and interfaces from your SCM repository:
Open editions of the classes and interfaces are created in the VisualAge for Java repository, and are added to your workspace.
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.
If you get 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 you retrieve its classes.
Retrieving Classes That Do Not Exist in the VisualAge for Java Repository
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 get the most
recently checked-in versions of classes that exist in the SCM repository but not in the
VisualAge for Java repository:
External SCM Tools (Windows)
Workspace
Editions and Versioning
Preparing to Use an External SCM Tool (Windows)
Setting Your SCM Connection Parameters (Windows)
Checking Classes Out from an External SCM Tool (Windows)
Checking Classes In with an External SCM Tool (Windows)
Importing Files from the File System
Undoing Checkout with an External SCM Tool (Windows)