Maybe by typing clean twice you can be _really_ sure your build is
clean ;)
I believe when you execute a command like m2 install, you are
invoking a lifecycle phase called 'install' and not a plugin. It just
so happens that default plugins are attached to these various phases
under the hood. The value you specify for the packaging pom element
dictates the set of plugins that are attached to the lifecycle
phases, so if you specify <packaging>jar</packaging> for example, you
can be sure that the jar plugin will be attached to the package phase.
However there is no concept of clean built into the lifecycle because
it would be really annoying if your build always performed a clean -
hence that functionality is rolled into a separate plugin.
But I think you're idea of a default goal is a good one.
AW
On 22 Sep 2005, at 21:35, Eli Doran wrote:
I have been wondering for some time why it is necessary to type "m2
clean:clean" instead of just "m2 clean". I understand it wants the
goal for the plugin but if the goal's name is not specified
couldn't it use a default goal? or at the very least check if it
has a goal of the exact same name to use; as in the 'clean'
example. It's just one of those things that makes me shake my head
and wonder why that is "the way it is". Doesn't anyone else get
annoyed at having to type "clean:clean" instead of just "clean" ?
~eli
---------------------------------------------------------------------
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]
