On Mon, 2009-05-18 at 09:18 +0200, Bocalinda wrote:
> Hi Alexander,
>
> Thank you for your response.
> Unfortunately your proposed solution will not work, as each module
> that I have (no matter which type it is; jar, war) will pass through
> all the steps of the build lifecycle, and thus will always execute the
> Cargo plugin. I only want it to be executed for WAR files.
>
> I'm really stuck, but I guess one can never give up :-)
Anyone familiar enough with Maven know how this should be handled?
> Thanks again for your help.
>
> 2009/5/16 Alexander Brill <
alex@...>
> On Thu, May 14, 2009 at 6:46 PM, Bocalinda
> <
bocalinda@...> wrote:
>
> When I execute Maven, I see that the Cargo plugin is
> executed for all modules, even for the Project Parent
> POM.
> I only want Cargo to be executed for Module3. I've
> been looking for a solution for the last three days,
> unfortunately without any success.
>
>
>
>
> This is most likely a maven2 question, and not really a cargo
> problem.
>
> You could try to reconfigure the executions of the cargo
> plugin in the specific module. Not sure if this would work,
> just a wild guess :)
>
> <plugin>
> ...
> <executions>
> <execution>
> <phase>package</phase>
> <goals>
> <goal></goal>
> </goals>
> </execution>
> </executions>
> ...
> </plugin>
>
>
> You can dig deeper into the matter by reading:
>
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html>
http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_executions_Tag>
>
>
> --
> Alexander Brill
>
http://brill.no>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email