[ http://jira.codehaus.org/browse/MPJAR-37?page=all ]
Jason van Zyl updated MPJAR-37:
-------------------------------
Assign To: (was: Jason van Zyl)
> maven.jar.manifest.classpath.add should work like ejb plugin
> ------------------------------------------------------------
>
> Key: MPJAR-37
> URL: http://jira.codehaus.org/browse/MPJAR-37
> Project: maven-jar-plugin
> Type: Bug
> Versions: 1.6
> Reporter: Dan Greening
>
> Original Estimate: 2 hours
> Remaining: 2 hours
>
> Setting maven.jar.manifest.classpath.add=true only adds the classpath to the
> jar file, but does not include the actual jars in the dependency.
> A much cleaner approach is provided by the EJB plugin, where you add
> properties in the POM dependencies, thus:
> <properties>
> <ejb.manifest.classpath>true</ejb.manifest.classpath>
> <ejb.bundle>true</ejb.bundle>
> </properties>
> For the JAR plugin it should be:
> <properties>
> <jar.manifest.classpath>true</jar.manifest.classpath>
> <jar.bundle>true</jar.bundle>
> </properties>
> And then, we should completely get rid of that
> maven.jar.manifest.classpath.add thing.
> A related issue (but not quite the same) appears in
> http://jira.codehaus.org/browse/MPJAR-25.
> An alternative approach, including a patch, was provided in
> http://jira.codehaus.org/browse/MPJAR-4, HOWEVER, the patch unzips the
> included jar files, complicating the jar file unnecessarily. (I suppose this
> could be an option, such as "maven.jar.explode.jars", to support J2ME, which
> cannot handle embedded jar files.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
