You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/06/13 02:15:14 UTC
[jira] Moved: (MSHARED-43) Class-Path manifest entry should support
maven repository layout
[ http://jira.codehaus.org/browse/MSHARED-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MNG-3332 to MSHARED-43:
------------------------------------------
Affects Version/s: (was: Reviewed Pending Version Assignment)
Fix Version/s: (was: Reviewed Pending Version Assignment)
Component/s: (was: maven-archiver)
maven-archiver
Key: MSHARED-43 (was: MNG-3332)
Project: Maven Shared Components (was: Maven 2)
> Class-Path manifest entry should support maven repository layout
> ----------------------------------------------------------------
>
> Key: MSHARED-43
> URL: http://jira.codehaus.org/browse/MSHARED-43
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-archiver
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
>
> 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