Hi,
Thanks for the prompt reply.
On 5/30/06, Edwin Punzalan <[EMAIL PROTECTED]> wrote:
use the assembly plugin's "attached" goal instead bec its bind to the
package phase. The assembly goal is there for the CLI only.
OK, I specified the 'attached' goal and bound the plugin to the 'package' phase:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<id>package-all</id>
<phase>package</phase>
<goals>
<goal>attached</goal>
</goals>
<configuration>
<descriptors>
<descriptor>src/main/assembly/package-all.xml</descriptor>
</descriptors>
</configuration>
</execution>
</executions>
</plugin>
Now Maven is calling the assembly plugin in each module. It then fails
because there is no
package-all.xml in the module src tree (package-all.xml lives in the
parent src).
Is this the expected behaviour?
I was wanting each module to simply build it's own jar as usual then
for the parent to collect all the module jars and bundle them up
together.
Adding an <inherited>false</inherited> section to the plugin
configuration didn't seem to help (but I don't really know if this is
what it's for :).
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
