On 3-Feb-08, at 2:55 PM, Vincent Siveton wrote:
Hi,
I realize that the fix for MPLUGIN-40 (All plugins should by default
have an auto-generated goal 'help') is definitely *not* intuitive for
the end user.
Background:
I created a plugin-plugin goal which generates an Help mojo. This
generated mojo just displays the goals and their
description/parameters for a given plugin project. Since it is a goal
inside the maven-plugin-plugin, we need to release it and *all*
plugins to make available this new feature (it could take a time ;) ).
I don't see a problem with that.
I proposed another approach: modify the DefaultLifecycleExecutor to
handle this particular goal.
No. Don't bind special logic for plugins internally. It's much easier
to release a tool in an external toolchain or fix a plugin.
The help plugin already does this doesn't it? Specify a particular
plugin and it gives you the goals. Did you take this logic and move it
to the plugin plugin?
So we could call "mvn idea:help" to
display all available idea goals and "mvn idea:toto" will throw an
exception by displaying the help.
Pro: more easy for the end user and works for all plugins
Con: just available in mvn 2.0.9+
WDYT?
Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
A man enjoys his work when he understands the whole and when he
is responsible for the quality of the whole
-- Christopher Alexander, A Pattern Language
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
