Every project from a certain ClearCase view that I try to import into JBoss Developer Studio 3.0.0GA comes in with every file marked as hijacked. When I view the project in ClearCase Explorer, the files are marked as expected, with only actual hijacked files marked as such. In JDS, I can manually go through the files and Undo the Hijack on them, which clears the “hijacked” badge from the icon, but afterwards I am then still unable to hijack any files. It seems that whatever mapping manages project file state between JDS and ClearCase has been corrupted.
I have both recreated my views from scratch and deleted my workspace in an attempt to clear the desynchronization, to no effect. Is there another location where the ClearCase SCM Adapter might be holding on to some settings related to this project, as unlikely as that sounds?
OK… this was all caused by my evil arch-enemy: me.
When a view is created, files in the view folder are set to “read-only” by default, and while working outside of the ClearCase sandbox and copying files in and out manually… I set the read-only flag on the entire view to
falsein the OS. So the ClearCase SCM adapter looks at the filesystem and sees all of these writable files and thinks, “Hm, these files aren’t checked out, but they’re writable, so they must be hijacked.”And thus the victory goes to the enemy and his legion of red Ø badges in Eclipse.