| Managed Make and ClearCase Best Practices [message #155378] |
Thu, 29 September 2005 10:19 |
Eclipse User |
|
|
|
Good morning all.
We've been working with Eclipse and the CDT for close to three years now.
And, since the beginning, we have had several challenges utilizing the CDT
effectively in our existing ClearCase environment. Challenges sever
enough that we have created our own Managed Make plug-in to correct issues
with the stock CDT Managed Make and ClearCase.
More specifically, we have a ClearCase environment that consists of mainly
Dynamic views and over 400 VOBs. The typical ClearCase user connects to
multiple VOBs in order to build a single product. That is, entire
projects typically do not reside in a single directory tree, much less a
single VOB.
To use the Eclipse project structure within our ClearCase environment,
we've had to utilize Eclipse linked resources to pull into a single
project all of the related source, models, and libraries (etc.) from
multiple VOBs. Our biggest headaches with this approach:
Complexity:
Linked resources, especially to ClearCase content, can be very confusing
for some users.
Performance:
Pulling in many files via dynamic views really drains performance. The
ClearCase plug-in within Eclipse tends to bog-down the system.
CDT Managed Make Fails:
Even as of CDT Managed Make 3.0, it does not function correctly with
linked resources. Specifically, you cannot specify a project's linked
resource as an include path.
In light of these issues, I ask how other companies are implementing the
CDT and ClearCase? How do you handle complex projects within Eclipse?
What have your experiences been migrating your existing ClearCase
environment to Eclipse?
Thank You,
Chad Barnes
Rockwell Collins, Inc.
|
|
|
Powered by
FUDForum. Page generated in 0.44016 seconds
Home