[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_68545 ]
Baerrach bonDierne commented on MASSEMBLY-67: --------------------------------------------- Brett, could you elaborate please? I'm not familiar with the archive section of the assembly plugin, but I am not sure how this would work anyway. (I can't find the archive definition at http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html and there is no information about the archive parameter at the mojo decriptions.) The jar file needs in META-INF/MANIFEST.MF entries like: Class-Path: <dep1> <dep2> etc so that I can just run on the command line: java -jar <jar file> So this would be part of the jar plugin. All the assembly's task is to create the correct directory structure so that the project's jar and all dependencies are copied to the correct locations so that the Class-Path declaration matches the file locations. Cheers > assembling dependent jars or snapshots uses timestamp formatted version > instead of ${version} > --------------------------------------------------------------------------------------------- > > Key: MASSEMBLY-67 > URL: http://jira.codehaus.org/browse/MASSEMBLY-67 > Project: Maven 2.x Assembly Plugin > Type: Bug > Reporter: Mark J. Titorenko > > > I'm using the jar plugin to add my dependencies to the manifest. I'm also > using the assembly plugin to package all dependencies into one archive. The > problem is that the jar manifest adds my dependencies as "foo-SNAPHOT" and > the archiver adds them as "foo-20041113.jar". > This causes my snapshot classes to not be found at runtime. -- 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
