use the assembly plugin's "attached" goal instead bec its bind to the
package phase. The assembly goal is there for the CLI only.
^_^
Deane Morrow wrote:
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
with all the module jars to produce the final application artifact.
I can use the assembly plugin fine from within a module.
I can't seem to get the assembly plugin to fire from the parent however.
Ideally, I'd like to be able to:
- configure an assembly descriptor in the parent
- run 'mvn package' from the parent
- have Maven package each module, then
- have the assembly from the parent produce the (parent) application
artifact
Does anyone know if this is possible?
It seems that the 'pom' packaging type in the parent may be hindering
the assembly. If this is the case, is there any way to achieve the
above?
The assembly plugin is configured in the parent as follows. I believe
it binds to the package phase by default?
<build>
...
<plugins>
...
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<id>assemble</id>
<configuration>
<descriptors>
<descriptor>src/main/assembly/descriptor.xml</descriptor>
</descriptors>
</configuration>
<goals>
<goal>assembly</goal>
</goals>
</execution>
</executions>
</plugin>
...
</plugins>
...
</build>
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
