[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=all ]
John Casey closed MASSEMBLY-67.
-------------------------------
Assignee: John Casey
Resolution: Fixed
The solution here is to use an outputFileNameMapping such as this:
${artifactId}-${baseVersion}.${extension}
Using ${baseVersion} for cases where you want to preserve the -SNAPSHOT naming,
the plugin retains the ability to use ${version} for the timestamp-buildnumber
naming, which is useful for describing the exact library version included in
the assembly.
I've added an integration test:
/basic-features/outputFileNameMapping-withArtifactBaseVersion to verify that
this is fixed.
> 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
> Assigned To: John Casey
> 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
