@phase xyz means you dont have to define phase in your plugin execution (
use default phase defined mojo). But you still need to define
your plugin executions.
However if you want hardwire to a phase when mojo is invoked from command
line use @execute. See maven-assembly-plugin for example.
-D
Look at it the other way. You've told maven that you are interested in
having this plugin execute at some point during your lifecycle but you
haven't defined which GOAL to execute. Remember a plugin can have N
goals. Maven should use the goal's default phase if you don't specify
the phase
Hi Dan,
Actually, what I want is the first option - I want that users of the
plugin *won't* have to define 'executions' - only specify my plugin in
their plugins section (along with optional configuration) and rely
on me to know at which phase to invoke.
Perhaps I'm getting it all wrong: as I
Hi Mike,
I'm not sure I follow - I specify the @phase inside my mojo (which
is basically a goal, right?) so as-far-as-I-understand maven should
know which goal to invoke...
On 2/1/06, Mike Perham [EMAIL PROTECTED] wrote:
Look at it the other way. You've told maven that you are interested in
A mojo is a goal, yes. What's to stop you from having two mojos, each
with the same default phase?
-Original Message-
From: Arik Kfir [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 31, 2006 6:02 PM
To: Maven Users List
Subject: Re: [m2] binding mojos to lifecycle
Hi Mike,
I'm
:[EMAIL PROTECTED]
Sent: Tuesday, January 31, 2006 6:02 PM
To: Maven Users List
Subject: Re: [m2] binding mojos to lifecycle
Hi Mike,
I'm not sure I follow - I specify the @phase inside my mojo (which is
basically a goal, right?) so as-far-as-I-understand maven should know
which goal
to stop you from having two mojos, each
with the same default phase?
-Original Message-
From: Arik Kfir [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 31, 2006 6:02 PM
To: Maven Users List
Subject: Re: [m2] binding mojos to lifecycle
Hi Mike,
I'm not sure I
