[ http://jira.codehaus.org/browse/MASSEMBLY-91?page=all ]
John Casey closed MASSEMBLY-91.
-------------------------------
Assignee: John Casey (was: Brett Porter)
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.
> Currently the assembly plugin renames SNAPSHOT dependencies to a date stamp
> ex. api-authorisation-4.00-20060502.150651-20.jar
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-91
> URL: http://jira.codehaus.org/browse/MASSEMBLY-91
> Project: Maven 2.x Assembly Plugin
> Issue Type: New Feature
> Affects Versions: 2.0.1
> Environment: Win XP, Java 1.5
> Reporter: Chris Stevenson
> Assigned To: John Casey
> Fix For: 2.2
>
>
> Currently the assembly plugin renames SNAPSHOT dependencies to a date stamp
> ex. api-authorisation-4.00-20060502.150651-20.jar. Would it be possible to
> offer a flag on the plugin so that this behaviour could be turned off and the
> file could remain as api-authorisation-SNAPSHOT.jar?
> The renaming of the files causes the files to become invalid when compiling
> native or CSharp binaries inside of maven.
> Thanks,
> Chris Stevenson
--
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
