Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Trivial
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: 1.10
-
Labels:None
Description
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 property):
<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>
Activity
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
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
jar files not in the maven repository should be added to project.xml using the standard maven jar override system.
The project should mantain the same set of dependencies both when built using maven than Eclipse, why should ypu need a dependency only when the project is built using eclipse?