[
https://jira.codehaus.org/browse/MASSEMBLY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340008#comment-340008
]
Karl Heinz Marbaise commented on MASSEMBLY-681:
-----------------------------------------------
If you take a look at the docs. The finalName is mentioned having a default
value of {{$\{project.build.finalName\}}} which means if no finalName is
defined the default will be used.
The result of the above is to make a difference between an empty tag
{{<finalName/>}} and a non existing tag at all. This will lead to a
contracdiction with the injected values in the Mojo.
This sounds to me we should go for an other way. May we have to introduce a
flag like {{noFinalName}} to suppress the finalName part but only in
relationship with {{formats: dir}}.
> 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: Bug
> Affects Versions: 2.4
> Reporter: Paul Millar
> Priority: Minor
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
