[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_70228 ]
Baerrach bonDierne commented on MASSEMBLY-67:
---------------------------------------------
I have provided refactoring, test cases and a patch to fix this bug on
MNG-2456, as it is not really a problem with the assembler.
I think the tight coupling of maven-archiver and assembler means that the use
of outputFileNameMapping in dependencySet should be deprecated as these
filenames must match.
> 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
> Fix For: 2.2
>
> 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
