You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2006/03/27 00:30:15 UTC

[jira] Updated: (MPJAR-46) Using maven.jar.manifest.classpath.add=true from maven console gives huge Class-Path

     [ http://jira.codehaus.org/browse/MPJAR-46?page=all ]

Lukas Theussl updated MPJAR-46:
-------------------------------

    Fix Version: 1.8

> Using maven.jar.manifest.classpath.add=true from maven console gives huge Class-Path
> ------------------------------------------------------------------------------------
>
>          Key: MPJAR-46
>          URL: http://jira.codehaus.org/browse/MPJAR-46
>      Project: maven-jar-plugin
>         Type: Bug

>     Reporter: Niklas Gustavsson
>      Fix For: 1.8

>
>
> When running maven console on a JAR where the manifest classpath is set using maven.jar.manifest.classpath.add=true, the classpath string is not reset between runs. So, if running the jar goal multiple times, the Class-Path attribute will be getting longer and longer, containing multiple copies of the classpath.
> This patch of plugin.jelly in maven-jar-plugin:
>   <j:set var="jarClasspath" value="${maven.jar.manifest.classpath.add}"/>
> + <j:set var="maven.jar.classpath" value=""/>
>   <j:if test="${jarClasspath}">
> fixes the problem but I'm unsure if it will affect something else.

-- 
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