Nick Neuberger wrote:
I was wondering why .classpath and .project are in the cvsignore file.
As did I. Probably it has some historical reason.
Is there a specific reason for this?I guess it has to do with different installations of clients. If we all agree on using maven as the primary build tool, then we could add .classpath and .project to the CVS repository. Then everyone could create a classpath variable in Eclipse named MAVEN_REPO which would point to the local maven repository. All library dependencies would be resolved against that variable. I.E. MAVEN_REPO/httpunit/jars/httpunit-1.5.4.jar and so on.
It is not even necessary for everyone to use maven as their build system (would be comfortable though), as long as everyone declares the MAVEN_REPO variable (when they use Eclipse) and mimic the repository structure of maven.
My 2cts.
Martijn
------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Jwebunit-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jwebunit-development
