1.0 Introduction
2.0 Supported software and specifications
3.0 Changes from the previous release
4.0 Known problems and limitations
4.1 Dynamic views and silently checking out files
4.2 Using ClearCase tools to modify source files
4.3 Multi-byte character set (DBCS) issues
4.4 "File has been removed from the file system" error
4.5 Loss of version history when renaming Java packages
4.6 Loss of version history when using drag-and-drop to copy or move a file into WebSphere Studio
4.7 Incorrect association of ClearCase views and UCM activities
4.8 Preference default setting: When checked in files are saved by an internal editor
This document describes functionality changes, known problems, limitations, and workarounds that are associated with using the ClearCase tools in WebSphere Studio.
For more information about the Rational ClearCase SCM adapter, refer to the online help. To view the online help for the ClearCase SCM adapter:
The help will only appear if you have installed the ClearCase SCM adapter.
- In WebSphere Studio, select Help > Help Contents.
- In the Help dialog box, select Rational ClearCase
The ClearCase SCM Adapter requires the following software:
- One of the following Windows platforms: 98, ME, NT 4.0, 2000, or XP Pro.
- WebSphere Studio Application Developer Version 5.
- ClearCase 4.2 or later (Full ClearCase or ClearCase LT) with the latest patches. Refer to the following table for the patch that is appropriate for your version of ClearCase:
ClearCase Version Patch Required 4.2 (Full ClearCase) clearcase_p4.2.NT-14 or later 4.2 (ClearCase LT) clearcase_lt_p2001A.04.00.NT-8 or later 2002.05.00 (Full ClearCase) clearcase_p2002.05.00.NT-7 or later 2002.05.00 (ClearCase LT) ClearCase LT 2002.05.20 or later To obtain ClearCase releases and patches, go to clearcase.rational.com or call Rational Support at 1-800-433-5444.
Note: Rational Software does not support the use of Windows XP Pro with ClearCase LT 4.2.
Applications built on top of Eclipse 2.0.1 are supported, such as WebSphere Studio Workbench 2.x, WebSphere Studio 5.0.x.
The following ClearCase options have changed or are no longer supported in the current version of the ClearCase SCM adapter:
- Automatically connect to ClearCase on startup Rational ClearCase Preferences option. Note that this option is on by default.
- If you import a project set file (a .psf file) that is not in a VOB using the File > Import > Team Project Set option, the ClearCase SCM adapter prompts you to choose a view from which to load the projects in the .psf file
- The Show Project Checkouts option is now called Find Checkouts
- When you perform ClearCase Deliver, Rebase, or Merge UCM operations, the ClearCase SCM adapter automatically refreshes any resources that have been affected. Note that you need the following patch to obtain this functionality: clearcase_p2002.05.00-NT-18 (or later) for full ClearCase.
The following options are new in the current version of the ClearCase SCM adapter:
- The Undo Hijack option on the Team context menu
- The Set default to check out files after adding them to source control Rational ClearCase Preferences option
- The Perform Refresh Status operations recursively Rational ClearCase Preferences option
- The Find Resources to Add to Source Control option on the ClearCase menu
- Hijacked files now display a Hijack decoration
For more information about these topics, refer to the online help for the ClearCase SCM adapter.
Within WebSphere Studio, 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 WebSphere Studio, 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.
Java .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 WebSphere Studio (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).
UCM activities containing multi-byte characters may appear to be corrupted in the Set Current Activity dialog.
Under certain circumstances, when attempting to add a "view private" file to source control, WebSphere Studio 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.
When WebSphere Studio refactors Java package names, it does not rename the package directory but, instead, deletes the old location and creates new files in the new location. As a result, WebSphere Studio does not retain the version history of the Java package. In addition, WebSphere Studio prompts you to add the Java package to source control.
When you attempt to overwrite a ClearCase element in WebSphere Studio with another version of the element from an external source using drag-and-drop, the version history of the ClearCase element is lost. In addition, WebSphere Studio prompts you to add the resource to source control.
If you are using multiple ClearCase views in the same workspace, UCM activities may not work correctly. In these cases, ClearCase may incorrectly associate an activity with a view or may use a different activity than the one you have selected. Likewise, if you are mixing UCM and non-UCM views in the same workspace, ClearCase may prompt you to select an activity for a non-UCM view or may not prompt you to select an activity for a UCM view. To avoid these types of problems, do not associate more than one ClearCase view with the same workspace.
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.
Return to the main readme file