12:42 p.m.
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?
1:03 p.m.
You have to use extensions of a classpath variable. The eclipse:eclipse
plugin uses M2_REPO as the variable by default. This common-core
.classpath file is an example:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="src/main/java"/>
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="var"
path="M2_REPO/apache-xerces/xml-apis/2.7.1/xml-apis-2.7.1.jar"/>
<classpathentry kind="var"
path="M2_REPO/apache-slide/webdavlib/2.0/webdavlib-2.0.jar"/>
<classpathentry kind="var"
path="M2_REPO/junit/junit/3.8.1/junit-3.8.1.jar"/>
<classpathentry kind="var"
path="M2_REPO/oswego-concurrent/concurrent/1.3.4/concurrent-1.3.4.jar"/>
<classpathentry kind="var"
path="M2_REPO/apache-httpclient/commons-httpclient/2.0.2/commons-httpclient-2.0.2.jar"/>
<classpathentry kind="var"
path="M2_REPO/apache-log4j/log4j/1.2.8/log4j-1.2.8.jar"/>
<classpathentry combineaccessrules="false" kind="src"
path="/common-logging-spi"/>
<classpathentry kind="output"
path="target/eclipse-classes"/>
</classpath>
You then have to define the M2_REPO classpath variable in your workspace
preferences.
Anil Saldhana wrote:
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
1:18 p.m.
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
6:58 a.m.
Or just run eclipse:eclipse
which will generate this from the maven pom file.
I think eclipse:eclipse (and the idea version if it exists?)
should be one of the build artifcats such that people
who modify pom also check in correct project files for IDEs.
On Tue, 2006-09-26 at 10:18 -0700, Johnson, Peter wrote:
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
--
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx
12:40 p.m.
I added an eclipse section to:
http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenBuildCreation
Kevin Conner wrote:
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
6420
days inactive
6421
days old
jboss-development@lists.jboss.org
5 comments
5 participants
participants (5)
-
Adrian Brock -
Anil Saldhana -
Johnson, Peter -
Kevin Conner -
Scott M Stark