-----Original Message----- Thanks for the feed-back. Good point about Eclipse touching the files. Other option is putting the files into a subdirectory as we used to have them. Also I could just post them on the wiki as you are thinking of doing with the POM.
My issue with maven is upkeep. If we have the ant build that everyone else is using and a POM for maven that only some are using there will be stuff that goes stale. Getting a maven generated .project & .classpath is a major win of using maven agreed. I believe the maven/ant discussion has been beaten to death on this list though and I for one don't want to open that up again ;-) -----/Original Message----- Why not create a sample project/classpath combo for the "used" (within the dev-team) IDE's and a readme specifying what to copy where and in the root-dir include them in .cvsignore (or whatever it is in svn). That way they will not be accidentaly updated in the repository, but are available to "jumpstart" a new developer... regards Alexander
