Okay, now I have few suggestions :) There are two ways people can(or does) import castor project in their eclipse workspace.
Case 1) Project per module :- - Checkout from console "svn co http://.."; - Generate settings using eclipse:eclipse - import project to eclipse (auto-find detects project based on eclipse settings) Case 2) Project for whole trunk. - Checkout using Subclipse (or some other hacky way) and have one project for whole code base. "mvn eclipse:eclipse" DOES NOT generate eclipse settings at parent level so "Case 2" folks will be unhappy and they will lost if those setting are not there. The parent level setting include classpathentry elements for src folders. Now, I agree with the problem of manually maintained classpath for any change of dependencies in maven configuration. But, "mvn eclipse:eclipse" does not solve problem for "Case 2" people. So, I think we can keep the parent level eclipse settings file and modify them to use m2eclipse plugin so that you don't have to maintain those class paths manually. How to add settings for m2eclipse. - Download and install m2eclipse. - enable m2eclipse nature. - remove the settings specifying complete *.jar location in classpath for maven dependencies and just add these which will take care of maven class path dependencies. <classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER" /> <classpathentry kind="var" path="M2_REPO"/> I have seen this at another project Mifos(http://mifos.org), everyone is fine with using m2eclipse plugin there. Udai --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
