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:
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
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.
[mailto:firstname.lastname@example.org] On Behalf Of Anil Saldhana
Sent: Tuesday, September 26, 2006 9:43 AM
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
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