Troubleshooting
Problem
This technote explains why projects migrated from previous versions of IBM® Rational® Application Developer (RAD) to version 7 using Rational ClearCase® show up as normal Java projects in the Project explorer view.
Cause
When projects are imported from ClearCase to RAD 7.x workspaces, files inside various projects are not really "checked-out" and they are marked as read-only.
Since autobuild is enabled by default in RAD, once projects are imported into the workspace, the build process (which includes the migration process) starts immediately.
The migration process will update certain files, for example, the .project file. Since those files are read-only, the migration process will not be able to complete successfully, which will result in many unexpected errors.
Resolving The Problem
- Turn autobuild off
- Check out the various projects requiring migration from ClearCase
- Ensure that all the .xxx files (especially any .project and .classpath files) are NOT read only
- Run a build, or re-enable auto build.
- If the EAR projects have not been migrated then open the .project file and manually add the following snippet and then run another build.
<buildCommand>
<name>com.ibm.etools.common.migration.MigrationBuilder</name>
<arguments>
</arguments>
</buildCommand>
What should be happening is that during the initial build process, the migration builder should prompt for check out the files (from ClearCase) that it is about to update. What maybe happening is that it is just by-passing them, and continuing the build process.
Was this topic helpful?
Document Information
Modified date:
10 September 2020
UID
swg21285443