Before you can use the check classes and interfaces in and out of an SCM tool, you must add them to source control in the SCM tool's repository. Before that, you must meet the prerequisites described in the file on preparing to use an external SCM tool. See the list of links below for more information.
In the VisualAge for Java IDE, you can select individual classes and interfaces that you wish to add to your SCM repository, as a preliminary step to checking them in and out. You can also select projects or packages in the IDE, as a convenient way to add all of their contained classes and interfaces to the SCM repository at once. There is no other relationship between projects and packages in VisualAge for Java, and the organizational constructs in your SCM tool. You will need to correlate the names, contents, and versions of your VisualAge for Java program elements with the elements stored in your SCM repository.
To add classes and interfaces from VisualAge for Java to source control in the SCM repository:
Wait for the Operation Complete dialog box to appear before you do any other software configuration tasks.
The classes and interfaces remain in your VisualAge for Java workspace and repository. When you want to change them, remember to check them out of the SCM repository. VisualAge for Java will does not enforce SCM checkout, but your SCM tool will not allow you to check in changes to program elements that you have not checked out.
As you create new classes and interfaces in your VisualAge for Java projects and packages, remember to add them to the SCM repository as well. There is no automated relationship between the VisualAge for Java source code repository and external SCM repositories.
To see where the classes and interfaces that you just added to the SCM repository are stored:
The team roles that
determine privileges within VisualAge for Java do not apply to external SCM tools. Any
member of the team can add any edition of a class or interface to the SCM repository,
regardless of who owns that program element in VisualAge for Java. SCM activities are
governed by the security policies of the SCM tool that you use.
External SCM Tools (Windows)
Preparing to Use an External SCM Tool (Windows)
Setting Your SCM Connection Parameters (Windows)
Versioning a Program Element
Checking Classes Out from an External SCM Tool (Windows)
Checking Classes In with an External SCM Tool (Windows)
Getting the Latest Version from an External SCM Tool (Windows)
Displaying SCM History (Windows)
Launching Your SCM Program (Windows)
Exporting Source Code to the File System