Rather naïve question. If each project migrates to maven2 and has an eclipse .classpath file, the dependent libraries all exist in local maven2 repository (which may be C:\xxxx\.m2\repository). How do we ensure that we can check in a .classpath file into the source repository just the way we do with our current build setup? _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Scott M Stark wrote: > You then have to define the M2_REPO classpath variable in your > workspace preferences. Maven can do this for you. mvn eclipse:add-maven-repo -Declipse.workspace=XXXXX Kev _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Don't include the jars directly. Instead, define a classpath variable, M2_REPO, in Eclipse and set it to c:/.../.m2/repository, and then include the jars as extensions./ For example, here is an extract from one of my .classpath files: <classpathentry sourcepath="M2_REPO/junit/junit/3.8.1/junit-3.8.1-sources.jar" kind="var" path="M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar"/> <classpathentry kind="var" path="M2_REPO/jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar"/> <classpathentry kind="var" path="M2_REPO/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar"/> <classpathentry sourcepath="M2_REPO/commons-lang/commons-lang/2.1/commons-lang-2.1-sources.jar" kind="var" path="M2_REPO/commons-lang/commons-lang/2.1/commons-lang-2.1.jar"/> If you do it this way, anybody can use the Eclipse projects as is. Peter Johnson | Consulting Engineer | Open Runtime Group - PDT - S&T Unisys | 25725 Jeronimo Road | Mission Viejo, CA 92691 | 949-380-6433 (n2 656-6433) Unisys imagine it. done. THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. -----Original Message----- From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Anil Saldhana Sent: Tuesday, September 26, 2006 9:43 AM To: JBoss.org development list Subject: [jboss-dev] Common eclipse .classpath for maven2 Rather naïve question. If each project migrates to maven2 and has an eclipse .classpath file, the dependent libraries all exist in local maven2 repository (which may be C:\xxxx\.m2\repository). How do we ensure that we can check in a .classpath file into the source repository just the way we do with our current build setup? _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development