You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2007/12/22 13:51:57 UTC
[jira] Moved: (MNG-3332) Class-Path manifest entry should support
maven repository layout
[ http://jira.codehaus.org/browse/MNG-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy moved MJAR-94 to MNG-3332:
---------------------------------------
Affects Version/s: (was: 2.1)
Reviewed Pending Version Assignment
Fix Version/s: (was: 2.2)
Reviewed Pending Version Assignment
Key: MNG-3332 (was: MJAR-94)
Project: Maven 2 (was: Maven 2.x Jar Plugin)
> Class-Path manifest entry should support maven repository layout
> ----------------------------------------------------------------
>
> Key: MNG-3332
> URL: http://jira.codehaus.org/browse/MNG-3332
> Project: Maven 2
> Issue Type: Improvement
> Components: maven-archiver
> Affects Versions: Reviewed Pending Version Assignment
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
> Fix For: Reviewed Pending Version Assignment
>
>
> 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