1.0 Introduction
2.0 Supported software and specifications
3.0 Installing the ClearCase SCM adapter
4.0 Changes from the previous major release
5.0 Known problems and limitations
5.1
Dynamic views and silently checking out files
5.2
Using ClearCase tools to modify source files
5.3
Preference default setting: When checked in files are saved by an internal editor
5.4
"File has been removed from the file system" error
5.5
Cannot import a project set file into a snapshot view
5.6
Undo Hijack does not work after saving changes
5.7 xclearcase crashes on Red Hat 8.x
5.8
Unable to install ClearCase or patches Red Hat 8.x
5.9
Cannot move resource to a non-versioned folder
This readme describes functionality changes, known problems, limitations, and workarounds that are associated with using the ClearCase tools in Eclipse.
For more information about the Rational ClearCase SCM adapter, refer the online Help. To view the online Help for the ClearCase SCM adapter:
Note: The online Help frequently refers to WebSphere Studio. For the purposes of the Help, you can interpret references to WebSphere Studio in the online Help as references to Eclipse.
The ClearCase Plugin requires the following software:
ClearCase Version Patch Required 4.2 (Full ClearCase) clearcase_p4.2-20 or later 4.2 (ClearCase LT) clearcase_lt_p4.2-9 or later 2002.05.00 (Full ClearCase) clearcase_p2002.05.00-10 or later 2002.05.20 (ClearCase LT) clearcase_lt_p2002.05.00-5 or later To obtain ClearCase releases and patches, go to http://www.rational.com/products/clearcase/.
Note: ClearCase patches are required for RedHat 7.3 support, and Red Hat Linux 7.3 is only supported in ClearCase 2002.05.00 or later.
Applications built on top of Eclipse 2.x are supported, such as WebSphere Studio Workbench 2.x, WebSphere Studio 5.0.x.
To install the ClearCase SCM adapter, take the following steps:
- Download the ClearCase cc_scmadapter-linux_2.2.1.35.zip file and extract the contents of the file to a directory in your file system.
- In Eclipse, choose Help > Software Updates > Update Manager. In the Feature Updates window, expand the My Computer entry, navigate to the directory that contains the contents of the scm_adapter.zip file, expand the ClearCaseSCMadapter folder, right-click on the eclipse folder, and choose Link Product Extension.
- The Install/Update dialog prompts you to restart the workbench. Choose Yes.
- In the Eclipse window, click Window > Customize Perspective.
- In the Customize Perspective dialog box, expand the Other entry, check the ClearCase option, and click OK.
The ClearCase menu option appears in the main menu of your Eclipse window, the ClearCase icons appear, and the installation of the ClearCase SCM adapter is complete.
The following ClearCase options have changed or are no longer supported in the current version of the ClearCase SCM adapter:
The following options are new in the current version of the ClearCase SCM adapter:
For more information about these topics, refer to the online Help for the ClearCase SCM adapter.
Within Eclipse, a few non-interactive editors may not check out files when first modified. If one of these editors edits a checked-in file that is under ClearCase control within Eclipse, these editors will silently check the file out of ClearCase automatically when they save the file. If you are using a shared branch within a dynamic view, the automatic check out process could create a potential problem. If you begin to edit a file that is not checked out, another user might check the file out, edit it, and check in a new version in the meantime. In this case, your changes will then overwrite the other user's changes when you save the file. Therefore, if you are using a shared branch within a dynamic view, you must check out files before editing them.
JavaTM .class files can get out of synch since the incremental compiler is not run when the user changes a file from any tool outside of Eclipse (such as Notepad or ClearCase merge tools). If you modify a file outside of the workbench you must perform a "Refresh" (from the context menu).
The default setting for the Rational ClearCase preference option called When checked in files are saved by an internal editor is Automatically checkout for the current release. This default setting will be changed to Do nothing in a future release.
Under certain circumstances, when attempting to add a "view private" file to source control, Eclipse posts an error message which reads: "File has been removed from the file system." This problem only occurs when the file is open in an editor. The file has not actually been deleted and this error message can be safely ignored.
If you export a project set file to a directory that is outside of a ClearCase view and then attempt to import the projects, ClearCase prompts you to select a dynamic view. If you want to import the projects from a snapshot view, you must first copy the project set file into a directory in the snapshot view you want to use.
Performing an Undo Hijack operation on a file after hijacking, editing, and saving it does not work. The workaround is to check the file out of ClearCase and then perform an Undo Checkout operation.
In release 8.0, Red Hat has changed the default value of the LANG environment variable to en_US.UTF-8, which ClearCase does not support. If you use ClearCase GUIs on Red Hat Linux 8.x, you must set the value of LANG in the /etc/sysconfig/i18n file to an encoding that ClearCase supports, such as C or en_US.iso885915. Once you have set the LANG environment variable to a value that ClearCase supports, make sure that the SUPPORTED variable in the i18n file also contains this value. If it does not, add this value to the SUPPORTED variable.
When attempting to install ClearCase or to apply ClearCase patches, an error message appears stating "Current directory incorrect." The problem is actually with Perl and is not due to an incorrect directory. The workaround is to install the Red Hat 8.x package compat-db-3.3.11, which provides libdb.so.3.
If you try to move a resource that is under ClearCase source control to a folder that is not under ClearCase source control, the move fails and an error message appears stating that ClearCase failed to add the parent directory to source control. The workaround is to place the destination folder under ClearCase source control.