[MJAR-83] addClasspath is not respected for runtime dependencies

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1, 2.2
• Fix Version/s: 2.2
• Assignee: Mauro Talevi
• Reporter: William Ferguson
• Created: 03/Sep/07 19:57
• Updated: 16/Oct/07 20:06
• Resolved: 13/Oct/07 08:03

Description

maven-jar-plugin does not resolve dependencies itself, so specifying

	<configuration>
		<archive>
			<manifest>
				<addClasspath>true</addClasspath>
			</manifest>
		</archive>
	</configuration>

will add no dependencies for

	mvn jar:jar

And even

	mvn compiler:compile jar:jar

will only add compile time dependencies, not runtime dependencies, presumably because the maven-compiler-plugin causes resolution of the compile time dependencies.

See the attached POM.
There is no manifest classpath generated by

	mvn jar:jar

The manifest classpath generated by

	mvn compiler:compile jar:jar

only contains commons-codec which is the compile time dependency.

There needs to be a way to add runtime dependences to the manifest classpath of the jar.
And preferably not requiring some other plugin to resolve the dependencies first.