[MJAR-41] Cannot specify additional classpath entries in jar manifest when using addClasspath

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0, 2.1
• Fix Version/s: 2.1
• Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK 1.5.0_06, Windows XP
• Assignee: Emmanuel Venisse
• Reporter: Fredrik Vraalsen
• Created: 09/May/06 05:34
• Updated: 22/Aug/06 07:51
• Resolved: 09/Aug/06 01:50

Description

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>

Issue Links

• is duplicated by: MJAR-55 possibility to add arbitrary elements to the manifest classpath