You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2014/12/04 19:59:10 UTC

[jira] (MASSEMBLY-681) plugin ignores empty finalName and uses default value

     [ https://jira.codehaus.org/browse/MASSEMBLY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Rosenvold updated MASSEMBLY-681:
-----------------------------------------

    Fix Version/s:     (was: 3.0)
                   backlog

> plugin ignores empty finalName and uses default value
> -----------------------------------------------------
>
>                 Key: MASSEMBLY-681
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-681
>             Project: Maven Assembly Plugin
>          Issue Type: Wish
>    Affects Versions: 2.4
>            Reporter: Paul Millar
>            Assignee: Karl-Heinz Marbaise
>            Priority: Minor
>             Fix For: backlog
>
>
> When used in the 'dir' format, I would argue that an empty finalName is reasonable.
> For example, I would expect the following configuration, with the 'dir' format, to output the assembled files in ${foo.baseDirectory}
>     <configuration>
>         <descriptors>
>           <descriptor>src/main/assembly/foo.xml</descriptor>
>         </descriptors>
>         <outputDirectory>${foo.baseDirectory}</outputDirectory>
>         <finalName/>
>     </configuration>
> The actual behaviour is to silently ignore the configured empty finalName and use the default finalName value, which is append this to the outputDirectory.
> Arguably there are two bugs here:
>     finalName is silently ignored (if this is invalid, it should report an error)
>     the empty finalName is not honoured.
> Specify '.' as the finalName (<finalName>.</finalName>) seems to work as a work-around, at least for unix-like systems.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)