[
https://jira.codehaus.org/browse/MASSEMBLY-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291558#comment-291558
]
Curtis Rueden commented on MASSEMBLY-91:
----------------------------------------
David: You can avoid using two separate configurations with the
"${dashClassifier?}" syntax:
<outputFileNameMapping>${artifact.artifactId}-${artifact.baseVersion}${dashClassifier?}.${artifact.extension}</outputFileNameMapping>
> Currently the assembly plugin renames SNAPSHOT dependencies to a date stamp
> ex. api-authorisation-4.00-20060502.150651-20.jar
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-91
> URL: https://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
> Assignee: John Casey
> Fix For: 2.2-beta-1
>
>
> 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
