[
http://jira.codehaus.org/browse/MASSEMBLY-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134005#action_134005
]
Michele Lorenzini commented on MASSEMBLY-300:
---------------------------------------------
Sorry, wrong copy & paste :o)
This was the outputFileNameMapping suggested in MASSEMBLY-91 which doesn't work
in 2-beta2:
${artifactId}-${baseVersion}.${extension}
This is the right outputFileNameMapping, works in 2-beta2:
${artifact.artifactId}-${artifact.baseVersion}.${artifact.extension}
> Regression: outputFileNameMapping variable resolution
> -----------------------------------------------------
>
> Key: MASSEMBLY-300
> URL: http://jira.codehaus.org/browse/MASSEMBLY-300
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Reporter: Daniel Spilker
>
> I am using
>
> <outputFileNameMapping>${artifactId}.${extension}</outputFileNameMapping>
> in a dependencySet with multiple includes.
> In 2.2-beta-1 the included artifactes where named by their artifactId and
> extension as specified by the outputFileNameMapping. In 2.2-beta-2 the files
> are named by the current project's artifactId and ${extension} is not
> resolved.
--
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
