[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259988#action_259988 ]
Craig edited comment on MASSEMBLY-67 at 3/14/11 12:31 AM: ---------------------------------------------------------- I just had problems somewhat related to this issue, but instead I was trying to get all timestamps for my snapshots. I wrote up my findings under another closed jira http://jira.codehaus.org/browse/MASSEMBLY-211?focusedCommentId=259987&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_259987 was (Author: craigb): I just had problems somewhat related to this issue, but instead I was trying to get all timestamps for my snapshots. I wrote up my findings under another close jira http://jira.codehaus.org/browse/MASSEMBLY-211?focusedCommentId=259987&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_259987 > 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 > Issue Type: Bug > Reporter: Mark J. Titorenko > Assignee: John Casey > Fix For: 2.2-beta-1 > > Attachments: MJAR-28-Notes.txt, MJAR-28-TestCases-Patch.txt > > > 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