You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Fredrik Vraalsen (JIRA)" <ji...@codehaus.org> on 2006/05/09 12:41:41 UTC
[jira] Commented: (MJAR-41) Cannot specify additional classpath
entries in jar manifest when using addClasspath
[ http://jira.codehaus.org/browse/MJAR-41?page=comments#action_65018 ]
Fredrik Vraalsen commented on MJAR-41:
--------------------------------------
See http://jira.codehaus.org/browse/MNG-2284 for a simple patch that solved the issue for me.
> Cannot specify additional classpath entries in jar manifest when using addClasspath
> -----------------------------------------------------------------------------------
>
> Key: MJAR-41
> URL: http://jira.codehaus.org/browse/MJAR-41
> Project: Maven 2.x Jar Plugin
> Type: Bug
> Versions: 2.1, 2.0
> Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK 1.5.0_06, Windows XP
> Reporter: Fredrik Vraalsen
>
>
> The plugin configuration snippet below leads to the generation of an illegal jar manifest file, as it contains two Class-Path entries. This works in Maven 1.1b2 by adding the following to project.properties:
> maven.jar.manifest.classpath.add=true
> maven.jar.classpath=help/ resources/
> For more information, please see http://www.nabble.com/classpath-in-jar-manifest-t1582724.html
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-jar-plugin</artifactId>
> <configuration>
> <archive>
> <manifest>
> <addClasspath>true</addClasspath>
> </manifest>
> <manifestEntries>
> <Class-Path>help/ resources/</Class-Path>
> </manifestEntries>
> </archive>
> </configuration>
> </plugin>
--
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