[
https://jira.codehaus.org/browse/MASSEMBLY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340829#comment-340829
]
Karl Heinz Marbaise commented on MASSEMBLY-681:
-----------------------------------------------
Sorry but my explanation wasn't accurate. The XML parser of Maven handles
everything well. The point is the injection mechanism in Maven says if the
value is not been set the default value will be injected. As a result of that
during the execution of a plugin it's usually not to distinguish if the values
hasn't been set at all or if the tags has been given empty.
> 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: 2.5
>
>
> 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)
