On Sunday 06 May 2007 16:39, David Corbin wrote: > That sound suspiciously like you've got a lot of duplication going on. > Fundamentally, Eclipse does NOT support heirarchies. I don't think you can > map a heiarchy to a flat model and maintain a one-to-one copy.
No. The plugin I pointed you to (and eclipse 3.1.x as well -- although it's not the default!) will not copy the directories, they will only link them! People have been able to do something like this for a pretty long time on *nix already, but it works fine on Win as well. The only problem you'll have is when deleting files in eclipse... Eclipse will recognize deletion ONLY on the project where you deleted! This means that you must synchronize that project seperately. Example: You have a parent-project A, with 2 sub-projects B and C. When you delete files in C, you must synchronize (and delete) these files from that project with your CVS. If you synchronize the project from A, eclipse will tell you that your SCM has newer versions for the deleted files! It has something to do with the internal remembering of deletions in eclipse, it is not an SCM-thing. > So, from what you say, If I have 3 layers in my heirarchy, Eclipse is going > to perceive 3 copies of every file in my bottom-most tier. No, you will have your project checked out only once, and eclipse references ONLY the java-type projects. If you have more than 1 layer, you will probably have 2 layers with POM-projects and 1 with actual Java-projects. The plugin will then only reference these projects, but leave the actual source-code in the original tree. -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
