[jboss-dev] Common eclipse .classpath for maven2

Scott M Stark scott.stark at jboss.org
Tue Sep 26 13:03:15 EDT 2006


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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>   




More information about the jboss-development mailing list