Some observations...
I've created a scratch project with four modules to try and understand
what is going on here.
I am configuring the assembly plugin in two different ways:
1. via the parent POM [1]
2. via the command line [2]
The two configuration methods are producing the same result [3] (a
Hi,
On 5/31/06, Barrie Treloar <[EMAIL PROTECTED]> wrote:
> 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?
Probably, because yo
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' p
Hi,
I have an application that follows the standard Maven project layout:
parent<--modules.
Each module produces a jar.
There is an additional module that contains the scripts required to
run and configure the application.
I am attempting to use the assembly plugin to bundle up the scripts
wit
