The problem is your include rule that filters out anything that doesn't
match it. Remove it and the dependencies would be included, only it would
then include all of your modules and their dependencies. I remember seeing
some talk about correcting the issue or maybe introducing a new syntax for
the behavior you expected in a new version. I've sometimes resorted to
creating a separate assembly pom that specifies just those module
dependencies I need to get the same effect.
Kalle
On 6/8/07, Kevin Stembridge <[EMAIL PROTECTED]> wrote:
Hi all,
I'm having a problem with the assembly plugin. It isn't including
dependencies for a binary within a module set. I have the following
configuration:
<moduleSet>
<includes>
<include>my.company:my-artifact</include>
</includes>
<binaries>
<includeDependencies>true</includeDependencies>
<useStrictFiltering>true</useStrictFiltering>
<outputDirectory>lib</outputDirectory>
<unpack>false</unpack>
</binaries>
</moduleSet>
The module artifact is included fine, but none of its dependencies. There
doesn't seem to be any issue raised for this problem yet. Just wondering
if anyone has seen it before.
Cheers,
Kevin
---
This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
