Hi Brett,

What do you propose for cmd line switch?

Personally, I am fine with mvn my-plugin:help which seems more common.
A lot of tools (all?) have an help option.

Cheers,

Vincent

2008/2/3, Brett Porter <[EMAIL PROTECTED]>:
> Would a different lifecycle or command line switch be more intuitive
> than this?
>
> On 04/02/2008, at 9:55 AM, 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 proposed another approach: modify the DefaultLifecycleExecutor to
> > handle this particular goal. 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]
> >
>
>
> ---------------------------------------------------------------------
> 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