maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Shute (JIRA)" <>
Subject [jira] Commented: (MPECLIPSE-85) Support for "lib" classpathentry
Date Tue, 14 Mar 2006 10:01:32 GMT
    [ ] 

James Shute commented on MPECLIPSE-85:

I have such a scenario.  My project uses xmlbeans - for ease of deployment and avoiding incompatibility
issues I want the xmlbeans generated classes to be in my jar.

This is easy to achieve with the main maven build, however it is not so easy to integrate
with Eclipse.

The most reliable way I have found (*) is to just add the jar that the xmlbeans build creates
as a reference in the eclipse project.  I don't want this jar to be public so putting it in
the repository as suggested is not appropriate.

To achieve this with the eclipse plugin as it stands I've had to set the maven.eclipse.classpath.include
property to include my jar file, and then use a <replace> in a post-goal to turn the
reference type into a lib, which is a bit ugly.

* I haven't been able to find any other approach that works for Eclipse that doesn't delete
all the .class files when you do a Project -> Clean

> Support for "lib" classpathentry
> --------------------------------
>          Key: MPECLIPSE-85
>          URL:
>      Project: maven-eclipse-plugin
>         Type: New Feature

>     Reporter: Flemming Seerup
>     Assignee: fabrizio giustina
>     Priority: Trivial
>      Fix For: 1.10

> To generate lib classpath entries for jar files not in maven repositories, I have added
the following code to classpath.jelly locally (after processing of maven.eclipse.conclasspath
> <u:tokenize var="libclasspaths" delim=",">${maven.eclipse.libclasspath}</u:tokenize>
> <j:forEach var="libclasspath" items="${libclasspaths}" trim="true">
>    <classpathentry kind="lib" path="${libclasspath}"/>
> </j:forEach>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message