In a ClearCase environment where .project and .cproject files are checked in (and thus read-only), CCS5.1 complains that it could not import a project because .cproject was write-protected. I can solve this problem by installing a ClearCase plugin for eclipse, which automatically checks out .project. But then everybody has different versions of .cproject and it is difficult to analyze if they really have been modified or not.
Could you please restore that behavior that worked until CCS5.1.05000? Else it is close to impossible to use CCS5.1 in a ClearCase environment where .project and .cproject files are shared via ClearCase. Keeping .project and .cproject as read-only does not work as described before ...
(this happens even when I do not switch configurations and do nothing more than importing a project - sometimes the files are simply checked out, although nothing is modified).
