maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michele Lorenzini (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MASSEMBLY-300) Regression: outputFileNameMapping variable resolution
Date Thu, 08 May 2008 13:53:27 GMT

    [ http://jira.codehaus.org/browse/MASSEMBLY-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134004#action_134004
] 

Michele Lorenzini commented on MASSEMBLY-300:
---------------------------------------------

I've found the same behaviour using the workaround described in MASSEMBLY-91 when using:

<outputFileNameMapping>somename-${baseVersion}.${extension}</outputFileNameMapping>

and passing to 2-beta2 version.

Resolved as commented by Benjamin with the artifact prefix:

<outputFileNameMapping>miobatch-${artifact.baseVersion}.${artifact.extension}</outputFileNameMapping>

this works in 2-beta2 also.
Regards

> 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

        

Mime
View raw message