[ http://jira.codehaus.org/browse/MJAR-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117279 ]
Olivier Lamy commented on MJAR-82: ---------------------------------- Oh yes. I have to add this in the jar plugin site. {code:xml} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> ... <configuration> <archive> <manifest> <addClasspath>true</addClasspath> <classPathMavenRepositoryLayout>true</classPathMavenRepositoryLayout> </manifest> </archive> </configuration> ... </plugin> {code} I have verfied (with unit test) the creation entry in the created MANIFEST but I haven't tried a jar with this. Thanks. > Class-Path manifest entry should support maven repository layout > ---------------------------------------------------------------- > > Key: MJAR-82 > URL: http://jira.codehaus.org/browse/MJAR-82 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement > Affects Versions: 2.1 > Reporter: Geoffrey De Smet > Assignee: Olivier Lamy > Fix For: 2.2 > > > 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>" -- 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