You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jerome Lacoste (JIRA)" <ji...@codehaus.org> on 2007/12/10 09:57:57 UTC
[jira] Commented: (MJAR-82) Class-Path manifest entry should
support maven repository layout
[ http://jira.codehaus.org/browse/MJAR-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116343 ]
Jerome Lacoste commented on MJAR-82:
------------------------------------
This one requires changes in the archiver, so fixing it would require releasing other modules. I would suggest to delay it if we want 2.2 out soon.
> 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
> 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