On 2 Nov 06, at 6:02 AM 2 Nov 06, Wendy Smoak wrote:
On 10/31/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Thinking about this, it may be a too harsh limitation of M2:
plugins are meant to
be independent of eachother, so you really shouldn't have to
execute several plugins
to achieve 1 task, or even set up something specific for another
plugin.
Consider...
http://docs.codehaus.org/display/MAVENUSER/Maven+and+Selenium
The 'unpacking' part has to happen before the 'copying' part.
How should I do this if I can't depend on execution order?
Ultimately this should be setup in a custom lifecycle so that it
becomes a recipe for using Selenium with Maven in addition to
everyone repeating this setup in their POM. Here we could probably
make some fake packaging so that we would wire up a lifecycle but I
think your example here indicates a need for a lifecycle that may not
necessarily be associated with a packaging. With a custom lifecycle
you have strick control over the ordering of goal execution.
So right now you could rip off the standard JAR lifecycle and then
all you would need to do is provide the configuration for the mojos
and maybe this could even be standardized for this lifecycle so that
you didn't have the provide configuration, just use some conventions.
Jason.
--
Wendy
---------------------------------------------------------------------
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]
