Thanks, John.

Is there an example of such a plugin in the maven codebase? I need to put
this together quickly to demo a proof-of-concept project

-Moiz 

-----Original Message-----
From: John Casey [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 28, 2005 11:49 AM
To: Maven Users List
Subject: Re: [m2] sequencing goals

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

one thing that springs to mind is to create an aggregator plugin that you
can bind into the lifecycle, which will call each of these mojos in
order...beyond that, it *may* work to add them in the order you desire
within an execution section under the plugin definition in the pom. I'm not
entirely sure whether this will work, though.

The aggregator mojo seems to be the most fool-proof, and it can handle
rough-grained integration into the lifecycle, while allowing each mojo
itself to stand alone for direct command-line invocation.

Does this seem reasonable? BTW, if you specify configuration at the plugin
definition level, it will be shared with all mojos within that plugin, where
the configuration is applicable.

HTH,

john

dohadwala, moiz wrote:
| I have a custom plugin with 3 goals. They are separate becuase I need
to be
| able to execute each one individually.
| They all bind to the same lifecycle phase.
|
| However, when the plugin is included in the build section, I need to
be able
| to execute all 3 goals, but in a pre-defined order:
| goal1->goal2>goal3.
|
| How do I enforce this in the plugin? If not, do I have to move them to 
| separate plugins? Then how do I enforce order between the plugins?
|
| -Moiz
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDOuWUK3h2CZwO/4URArJOAKCqlz/h6fdxYgGMcsPZkVI/RzvSjQCgnrWH
C9g3FWBcpyzsAlvbXDcb5Rs=
=DhA2
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
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]

Reply via email to