[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=comments#action_64578 ]
Jason Chaffee commented on MASSEMBLY-89: ---------------------------------------- I am seeing the same behavior when building the assembly plugin from the trunk. Basically, it is interpolating all ${artifactId} in the assembly descriptor xml and changing them to be the project.artifactId. For example, in my pom.xml my artifactId is "packger". Let's say I have two jars in my pom, test-1.0.jar and foo-1.0.jar. If I use ${artifactId}.${extension} for the outputFileNameMapping I will end up with only one artifact in my bundle and it will have the name packager.jar. If I use ${artifactId}-${version}.${extension} then I will get the correct behavior and I will see both test-1.0.jar and foo-1.0.jar. Therefore, it seems the interoplation isn't happening if ${version} is used which is very strange. > 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