Known problems and limitations

The following list describes known problems and limitations associated with the ClearCase SCM Adapter.

Dynamic views and automatic checkout

Within Rational Developer products, 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 in the Rational Developer product, these editors automatically check out the file when they save it. If you are using a shared branch in 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 overwrite the other user's changes when you save the file. If you are using a shared branch within a dynamic view, you must check out files before editing them.  

Using ClearCase tools to modify source files

JavaTM .class files can get out of synch because the incremental compiler does not run when the user changes a file from any tool outside the Rational Developer product (such as Notepad or ClearCase Diff Merge tools). If you modify a file outside the Rational Developer workbench, right-click the element and click Refresh.

"File has been removed from the file system" error

Under some circumstances, when you attempt to add a view private file to source control, the Rational Developer product displays this error message: "File has been removed from the file system." This problem occurs only when the file is open in an editor. The file has not been deleted and this error message can be ignored.

Renaming a package fails because new folder is not under source control

When using ClearCase 2002.05.x, renaming a package in Eclipse or the Rational Developer product fails if the new folder is not under source control. The error occurs because these versions of ClearCase cannot add folders to source control silently. After the error message appears, ClearCase may prompt you to add the folder to source control. Add the folder to source control and then repeat the rename operation. If you are not prompted, select the folder and choose ClearCase > Add to Source Control, and repeat the rename operation.

Refactoring

When you perform a refactor operation, the ClearCase SCM Adapter may prompt you with a list of files to check out. If you clear the check box associated with any of the files in the Check Out Element(s) dialog box, the refactor operation fails. The workaround is to allow the ClearCase SCM Adapter to check out all the files, then undo the checkout for the files that you do not want to check out.

Files show as view-private after reconnecting to ClearCase

When you disconnect from ClearCase, disable and then enable your network connection, and then reconnect to ClearCase, your project files may appear in the workspace as view-private. ClearCase menu options for the project may also be inactive. The workaround is to wait until ClearCase services restart before attempting to reconnect to ClearCase.

Adding ClearCase to your perspective

ClearCase menus may not appear in some perspectives in Rational Developer products. The workaround is to manually add ClearCase to the perspective by clicking Windows > Customize Perspective, selecting the Comments tab, and checking the ClearCase option in the Available Command Group list box

Failing to preserve case in mixed environments can produce compile errors

When working in a mixed environment, take the following steps to avoid compile errors caused by case-inconsistent file names:

  1. In the Windows Control Panel, click ClearCase.
  2. In the ClearCase Properties dialog, click the MVFS tab.
  3. Make sure the Case Insensitive MVFS and the Case Preserving options are selected.

If these options are not selected, you may experience compile errors because the case of the file names is different.

Windows only indicator  Dynamic views do not start automatically

In ClearCase version 2003.06.x, dynamic views do not start automatically after you reboot your machine. When you try to open a project in the Rational Developer product after rebooting, you may see an error message that states that the .project file is missing. The workaround is to start your views manually in ClearCase after rebooting.

Linux only indicator  Undo Hijack does not work after saving changes

An Undo Hijack operation performed on a file after you hijack, edit, and save it does not work. The workaround is to check out the file and cancel the checkout operation using Undo Check Out.

Linux only indicator  xclearcase crashes on Red Hat Linux 8.x

If you are running on any of the following platforms: 

RedHat Professional 8 and 9, RHEL 2.1 and 3.0, or SLES9

ClearCase does not support a LANG environment variable that contains UTF-8. If you use ClearCase GUIs on these platforms, you must set the value of LANG in the /etc/sysconfig/i18n file to a supported value, such as C or en_US.iso885915. After you reset the LANG environment variable, verify that the SUPPORTED variable in the i18n file also contains this value. If it does not, add this value to the SUPPORTED variable.

Linux only indicator  Unable to install ClearCase or apply patches under Red Hat Linux 8.x

When you attempt to install ClearCase or to apply ClearCase patches, you see this error message: "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 Linux 8.x package compat-db-3.3.11, which provides libdb.so.3.

Linux only indicator  Cannot move resource to a non-versioned folder

If you try to move a resource that is under source control to a folder that is not under source control, the move fails and an error message states that ClearCase failed to add the parent directory to source control. The workaround is to place the destination folder under source control.