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
Preference default setting: When checked in files are saved by an internal
editor
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
This readme describes functionality changes, known problems, limitations, and workarounds that are associated with using the ClearCase tools in WebSphereR Studio.
For more information about the Rational ClearCase SCM adapter, refer the online Help. To view the online Help for the ClearCase SCM adapter:
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.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:
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 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.
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 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).
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, 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 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.