[MJAR-82] Class-Path manifest entry should support maven repository layout

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.2
• Assignee: Olivier Lamy
• Reporter: Geoffrey De Smet
• Created: 27/Aug/07 09:33
• Updated: 06/Apr/15 01:16
• Resolved: 02/Jan/08 16:50

Description

The assembly plugin supports outputting all dependencies in a repository layout.
The jar plugin should support adding the classpath manifest entry based on the repository layout.
The combination of the two makes it easy to write a script to run the app: "java -jar org/domain/project/projectApp.jar" at the base of the repository layout.

Example of a Class-Path entry:
ClassPath: org/springframework/spring-core/2.0/spring-core-2.0.jar;org/drools/drools-core/4.0/drools-core-4.0.jar;org/domain/project/projectApp.jar

Also see maven user mailing list "maven-jar-plugin: how to avoid conflicts in <addClasspath>"

Issue Links

• depends upon: MSHARED-43 Class-Path manifest entry should support maven repository layout