You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by zosrothko <zo...@orange.fr> on 2011/04/22 11:30:56 UTC
multi-module project and order of plugin execution
Hi
I have a multi module project like
MMP
|----A
|----B
|----C
I am using the maven-antrun-plugin to execute an ant task but for the goal
install, the execution of this plugin takes place before the
compilation/test of the sub module A/B/C. How could I specify that this
execution be run by the end??
TIA
--
View this message in context: http://maven.40175.n5.nabble.com/multi-module-project-and-order-of-plugin-execution-tp4332618p4332618.html
Sent from the Maven - Users mailing list archive at Nabble.com.
Re: multi-module project and order of plugin execution
Posted by Ron Wheeler <rw...@artifact-software.com>.
On 26/04/2011 9:00 AM, Francis ANDRE wrote:
>> Regardless who's opinion is right, this is how it works in Maven as well.
> My view is more a post order walk than a pre order walk. Thus how can I
> specify that the multimodule should be the last in the reactor? (my multi
> module, which is an assembly step is depending on the jars produced by its
> sons and not the contrary)
>
A parent is used to specify project deployment repositories, versions of
common dependencies, defaults for plug-ins, etc..
It does not usually build anything.
An assembly is just an ordinary module that depends on other modules so
it will get built in the right order.
Ron
> zosrothko
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: multi-module project and order of plugin execution
Posted by Joachim Van der Auwera <jo...@progs.be>.
Why not create a separate module to build the assembly and have that
module depend on the other modules it needs. That should do the trick.
Kind regards,
Joachim
On 04/26/2011 03:00 PM, Francis ANDRE wrote:
>> Regardless who's opinion is right, this is how it works in Maven as well.
> My view is more a post order walk than a pre order walk. Thus how can I
> specify that the multimodule should be the last in the reactor? (my multi
> module, which is an assembly step is depending on the jars produced by its
> sons and not the contrary)
>
> zosrothko
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: multi-module project and order of plugin execution
Posted by Francis ANDRE <fr...@orange.fr>.
> Regardless who's opinion is right, this is how it works in Maven as well.
My view is more a post order walk than a pre order walk. Thus how can I
specify that the multimodule should be the last in the reactor? (my multi
module, which is an assembly step is depending on the jars produced by its
sons and not the contrary)
zosrothko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: multi-module project and order of plugin execution
Posted by Anders Hammar <an...@hammar.net>.
Compare it to the relationship between a Java class and a super-class it
extends. The super-class has to be compiled before the class extending it.
Regardless who's opinion is right, this is how it works in Maven as well.
/Anders
On Tue, Apr 26, 2011 at 13:59, zosrothko <zo...@orange.fr> wrote:
>
> Anders Hammar wrote:
> >
> > Yes, you are wrong. The parent has to be computed before the child.
> >
> > /Anders
> >
> > On Mon, Apr 25, 2011 at 12:14, zosrothko <zosrothko@orange.fr>
> > wrote:
> >
> >
>
> Can you be more explicit because otherwise I consider my position as
> correct. There is no dependency relationship between any submodule and the
> multi module, only a containment or inheritance relationship.
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/multi-module-project-and-order-of-plugin-execution-tp4332618p4340775.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: multi-module project and order of plugin execution
Posted by zosrothko <zo...@orange.fr>.
Anders Hammar wrote:
>
> Yes, you are wrong. The parent has to be computed before the child.
>
> /Anders
>
> On Mon, Apr 25, 2011 at 12:14, zosrothko <zosrothko@orange.fr>
> wrote:
>
>
Can you be more explicit because otherwise I consider my position as
correct. There is no dependency relationship between any submodule and the
multi module, only a containment or inheritance relationship.
--
View this message in context: http://maven.40175.n5.nabble.com/multi-module-project-and-order-of-plugin-execution-tp4332618p4340775.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: multi-module project and order of plugin execution
Posted by Anders Hammar <an...@hammar.net>.
Yes, you are wrong. The parent has to be computed before the child.
/Anders
On Mon, Apr 25, 2011 at 12:14, zosrothko <zo...@orange.fr> wrote:
> Hi
>
> I am lost...
>
> Following is the execution for mvn clean. The multi module pom is "An ISO
> compliant stack" while all others are sub modules. The order computed by
> the
> reactor is the same for mvn install while I want the 'ISO compliant stack"
> pom be executed by the end...
>
> Moreover, I found
> http://maven.apache.org/plugins/maven-assembly-plugin/faq.html this
> remark
> in the documentation of the maven-assembly-plugin :
>
> "In a multimodule hierarchy, when a child module declares the parent POM in
> its <parent/> section, Maven interprets this to mean that the parent
> project's build must be completed before the child build can start. This
> ensures that the parent project is in its final form by the time the child
> needs access to its POM information."
>
> If this is true, then this explain the order of the reactor...but this is a
> bug IMO... The fact to consider a <parent> link between a son module and
> its
> father as a dependency is wrong... Only the order computed by the reactor
> should be the one expresses by the dependencies. If a son module is
> dependent of its parent, this latest should be expressed in the
> </dependencies> element of the son's pom, not as an overinterpretation of
> the <parent> tag. Am I wrong??
>
>
>
> D:\OSI\iso-itu-osi-als>mvn clean
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] An ISO compliant stack
> [INFO] iso-itu-osi-als-osi
> [INFO] iso-itu-osi-als-nsap
> [INFO] iso-itu-osi-als-tsap
> [INFO] iso-itu-osi-als-ssap
> [INFO] iso-itu-osi-als-psap
> [INFO] iso-itu-osi-als-acsap
> [INFO] iso-itu-osi-als-rosap
> [INFO] iso-itu-osi-als-rtsap
> [INFO] iso-itu-osi-als-ccrse
> [INFO] iso-itu-osi-als-demo
> [INFO] iso-itu-osi-als-tools
> [INFO] iso-itu-osi-als-i4j
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building An ISO compliant stack 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ iso-itu-osi-als
> ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-osi 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-osi ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-osi\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-nsap 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-nsap ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-nsap\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-tsap 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-tsap ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-tsap\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-ssap 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-ssap ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-ssap\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-psap 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-psap ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-psap\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-acsap 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-acsap ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-acsap\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-rosap 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-rosap ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-rosap\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-rtsap 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-rtsap ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-rtsap\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-ccrse 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-ccrse ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-ccrse\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-demo 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-demo ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-demo\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-tools 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-tools ---
> [INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-tools\target
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building iso-itu-osi-als-i4j 2.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> iso-itu-osi-als-i4j ---
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] An ISO compliant stack ............................ SUCCESS [4.031s]
> [INFO] iso-itu-osi-als-osi ............................... SUCCESS [0.922s]
> [INFO] iso-itu-osi-als-nsap .............................. SUCCESS [0.375s]
> [INFO] iso-itu-osi-als-tsap .............................. SUCCESS [0.453s]
> [INFO] iso-itu-osi-als-ssap .............................. SUCCESS [1.500s]
> [INFO] iso-itu-osi-als-psap .............................. SUCCESS [0.375s]
> [INFO] iso-itu-osi-als-acsap ............................. SUCCESS [0.516s]
> [INFO] iso-itu-osi-als-rosap ............................. SUCCESS [0.312s]
> [INFO] iso-itu-osi-als-rtsap ............................. SUCCESS [0.297s]
> [INFO] iso-itu-osi-als-ccrse ............................. SUCCESS [0.438s]
> [INFO] iso-itu-osi-als-demo .............................. SUCCESS [0.765s]
> [INFO] iso-itu-osi-als-tools ............................. SUCCESS [0.172s]
> [INFO] iso-itu-osi-als-i4j ............................... SUCCESS [0.063s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 10.625s
> [INFO] Finished at: Mon Apr 25 11:57:11 CEST 2011
> [INFO] Final Memory: 2M/5M
> [INFO]
> ------------------------------------------------------------------------
> D:\OSI\iso-itu-osi-als>
>
>
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/multi-module-project-and-order-of-plugin-execution-tp4332618p4338018.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: multi-module project and order of plugin execution
Posted by zosrothko <zo...@orange.fr>.
Hi
I am lost...
Following is the execution for mvn clean. The multi module pom is "An ISO
compliant stack" while all others are sub modules. The order computed by the
reactor is the same for mvn install while I want the 'ISO compliant stack"
pom be executed by the end...
Moreover, I found
http://maven.apache.org/plugins/maven-assembly-plugin/faq.html this remark
in the documentation of the maven-assembly-plugin :
"In a multimodule hierarchy, when a child module declares the parent POM in
its <parent/> section, Maven interprets this to mean that the parent
project's build must be completed before the child build can start. This
ensures that the parent project is in its final form by the time the child
needs access to its POM information."
If this is true, then this explain the order of the reactor...but this is a
bug IMO... The fact to consider a <parent> link between a son module and its
father as a dependency is wrong... Only the order computed by the reactor
should be the one expresses by the dependencies. If a son module is
dependent of its parent, this latest should be expressed in the
</dependencies> element of the son's pom, not as an overinterpretation of
the <parent> tag. Am I wrong??
D:\OSI\iso-itu-osi-als>mvn clean
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] An ISO compliant stack
[INFO] iso-itu-osi-als-osi
[INFO] iso-itu-osi-als-nsap
[INFO] iso-itu-osi-als-tsap
[INFO] iso-itu-osi-als-ssap
[INFO] iso-itu-osi-als-psap
[INFO] iso-itu-osi-als-acsap
[INFO] iso-itu-osi-als-rosap
[INFO] iso-itu-osi-als-rtsap
[INFO] iso-itu-osi-als-ccrse
[INFO] iso-itu-osi-als-demo
[INFO] iso-itu-osi-als-tools
[INFO] iso-itu-osi-als-i4j
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building An ISO compliant stack 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ iso-itu-osi-als
---
[INFO] Deleting D:\OSI\iso-itu-osi-als\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-osi 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-osi ---
[INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-osi\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-nsap 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-nsap ---
[INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-nsap\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-tsap 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-tsap ---
[INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-tsap\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-ssap 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-ssap ---
[INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-ssap\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-psap 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-psap ---
[INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-psap\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-acsap 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-acsap ---
[INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-acsap\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-rosap 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-rosap ---
[INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-rosap\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-rtsap 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-rtsap ---
[INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-rtsap\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-ccrse 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-ccrse ---
[INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-ccrse\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-demo 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-demo ---
[INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-demo\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-tools 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-tools ---
[INFO] Deleting D:\OSI\iso-itu-osi-als\iso-itu-osi-als-tools\target
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building iso-itu-osi-als-i4j 2.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
iso-itu-osi-als-i4j ---
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] An ISO compliant stack ............................ SUCCESS [4.031s]
[INFO] iso-itu-osi-als-osi ............................... SUCCESS [0.922s]
[INFO] iso-itu-osi-als-nsap .............................. SUCCESS [0.375s]
[INFO] iso-itu-osi-als-tsap .............................. SUCCESS [0.453s]
[INFO] iso-itu-osi-als-ssap .............................. SUCCESS [1.500s]
[INFO] iso-itu-osi-als-psap .............................. SUCCESS [0.375s]
[INFO] iso-itu-osi-als-acsap ............................. SUCCESS [0.516s]
[INFO] iso-itu-osi-als-rosap ............................. SUCCESS [0.312s]
[INFO] iso-itu-osi-als-rtsap ............................. SUCCESS [0.297s]
[INFO] iso-itu-osi-als-ccrse ............................. SUCCESS [0.438s]
[INFO] iso-itu-osi-als-demo .............................. SUCCESS [0.765s]
[INFO] iso-itu-osi-als-tools ............................. SUCCESS [0.172s]
[INFO] iso-itu-osi-als-i4j ............................... SUCCESS [0.063s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 10.625s
[INFO] Finished at: Mon Apr 25 11:57:11 CEST 2011
[INFO] Final Memory: 2M/5M
[INFO]
------------------------------------------------------------------------
D:\OSI\iso-itu-osi-als>
--
View this message in context: http://maven.40175.n5.nabble.com/multi-module-project-and-order-of-plugin-execution-tp4332618p4338018.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: multi-module project and order of plugin execution
Posted by "maxime.lem" <ma...@gmail.com>.
> the execution of this plugin takes place before the compilation/test of the
sub module A/B/C
Just to be sure, in a multi-module project, maven runs its lifecycle until
the specified phase on a module, and then switch to the next module.
You have to distinguish if your problem is a wrong order of modules being
built in maven reactor, or a wrong order of goals run in a lifecycle.
First one is determine according to relationships/dependencies between
modules.
Second one is determine according goals bound to phases for the active
lifecycle.
--
View this message in context: http://maven.40175.n5.nabble.com/multi-module-project-and-order-of-plugin-execution-tp4332618p4333954.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: multi-module project and order of plugin execution
Posted by zosrothko <zo...@orange.fr>.
Hi Karl
I already put the plugin with a phase of package and it always run first.
> why do you need maven-antrun plugin
the maven-antrun plugin is used to run the packager install4j that builds up
an installer. Thus it needs all jars beeing made before it can package them.
Thus it should by the end of the mvn run.
>second what would you like to do with that?
See previous answer.
Rgds
--
View this message in context: http://maven.40175.n5.nabble.com/multi-module-project-and-order-of-plugin-execution-tp4332618p4333414.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: multi-module project and order of plugin execution
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,
> compilation/test of the sub module A/B/C. How could I specify that this
Two questions about that: First why do you need the maven-antrun plugin
and second what would you like to do with that?
Furthermore you can pust the antrun into a different phase like verify
which run's before install...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org