Smells like a bug...

On 14 December 2011 12:42, Antonio Petrelli <[email protected]> wrote:
> Hi all
> I am writing here since I don't know if it is a bug, and if yes, if it is a
> bug of Maven core or the assembly plugin.
> I am using assembly plugin version 2.2.2 and 2.2.3-SNAPSHOT compiled from
> source.
> When I add a dependency of this type (notice the empty classifier element):
>
> [snip]
>    <dependency>
>      <groupId>org.apache.tiles</groupId>
>      <artifactId>tiles-api</artifactId>
>      <version>2.2.2</version>
>      <classifier />
>    </dependency>
> [/snip]
>
> and I put it inside the assembly descriptor:
> [snip]
>  <dependencySets>
>    <dependencySet>
>      <outputDirectory>/</outputDirectory>
>    </dependencySet>
>  </dependencySets>
> [/snip]
>
> I see that the tiles-api jar contains an extra dash in its name:
> tiles-api-2.2.2-.jar
>
> Is this the intended behaviour? In spite of the empty classifier, WARs and
> EARs are correctly created, while assemblies are not.
>
> Though a minor bug, I think this is a bug. WDYT?
> I prepared a test case that I will submit with the bug report. I would like
> to fix it but I don't know if it is best to fix it at Maven level or
> Assembly Plugin level.
>
> Thanks
> Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to