[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_68546 ]
Brett Porter commented on MASSEMBLY-67: --------------------------------------- <archive> is in the configuration element (like it is for a JAR). I think it should also be supported in the assembly descriptor, but that's a separate issue as it isn't right now. http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html So, this allows you to write out the archive configuration if the assembly is producing a JAR in the same way as if you were just producing a JAR. > 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
