[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=all ]
John Casey closed MASSEMBLY-89:
-------------------------------
Resolution: Fixed
I fixed this by adding an interpolation-blacklisting of certain elements within
the outputFileNameMapping element. This approach is extensible, should we ever
have another element with a similar problem. I've also added a unit test for
this specific case. My changes can be seen in SVN revision 399323.
Jason: I'm not sure if you noticed where filterFile(..) is called, but it's
used for processing file entries in the descriptor, and filtering tokens in
those...not in loading the assembly descriptor itself.
> outputFileNameMapping broken
> ----------------------------
>
> Key: MASSEMBLY-89
> URL: http://jira.codehaus.org/browse/MASSEMBLY-89
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1
> Environment: xp
> Reporter: Dan Tran
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.1
> Attachments: bin.xml, pom.xml
>
>
> Prior to MASSEMBLY-40, I am able to outputFileNameMapping feature to place
> all dependency aritifacts into assembly without the version
> Here is an exmple
> <dependencySets>
> <dependencySet>
>
> <outputFileNameMapping>${artifactId}.${extension}</outputFileNameMapping>
> </dependencySet>
> </depenendencySets>
> After MASSEMBLY40, All artifact inside a set of dependencySet is mapped to
> a single file ${artifactId}.${extention}
--
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
