[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_118978 ] Olivier Lamy commented on MJAR-82: -- have a look at the it MJAR-82 in the jar plugin (the directory of the jar is used). 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
[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_118597 ] Geoffrey De Smet commented on MJAR-82: -- I 've tested it and it looks ok. I haven't been able to test it with the assembly plugin combined with java -jar, because of our hack for MJAR-28 which needs a dependencySet, so we can't use a repository. I am unsure if the Class-path is taken from the current working directory or from the directory of the jar. In the second case that might mean that all entry's should be prefixed with ../../, depending on the number of dots in the groupId of the jar. I 'll create another issue and reference it here if that's the case. 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
[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_118320 ] Olivier Lamy commented on MJAR-82: -- Geoffrey did you have time to test this feature ? 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
[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_118324 ] Olivier Lamy commented on MJAR-82: -- everything is deployed (maven-archiver et jar plugin). 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
[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_117279
]
Olivier Lamy commented on MJAR-82:
--
Oh yes. I have to add this in the jar plugin site.
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
...
configuration
archive
manifest
addClasspathtrue/addClasspath
classPathMavenRepositoryLayouttrue/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
[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_117223 ] Geoffrey De Smet commented on MJAR-82: -- Thanks :) What's the configuration entry to turn this feature on? 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
[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_117166 ] Olivier Lamy commented on MJAR-82: -- Support of this has been committed in maven-archiver rev 605055. Before closing I'd like to write it test in jar-plugin. But if someone want to test he can :-) 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
[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
