Auto-checkout of dependant files when refactoring projects using ClearCase

Abstract: Auto-checkout of dependant files when refactoring projects using ClearCase

Issue:

When evaluating refactorings for a large ClearCase integrated project, often it is the case that many of the dependant files necessary to proceed with the refactoring are read-only and require being checkedout. Does JBuilder provide any features to assist with this process?

Solution:

JBuilder offers support for handling ClearCase read-only files via refactoring. This requires an active connection to the ClearCase server so checkouts can occur. This feature is supported with both static and dynamic views.

The file where you initiate the refactoring must be checked out. If changes need to be made to files which are read-only, a console in the Message pane will list them, and you can initiate an automatic checkout of those files from that console, then tell it to proceed with the refactoring.

If you are not connected to the ClearCase server, there isn't any support to instead hijack the read-only files and later convert those to checkouts when they do become connected. In this case, you would have to hijack the file where refactoring is to be initiated, and ultimately have to hijack manually each file that refactoring needs to modify.