-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
I wrote:
> I would prefer that if maven builds a plugin that has no goal "help" already,
> then it auto-generates one in about the same way as it does
> when generating the goal-documentation for the site. Then each plugin
> would have (in f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
>>> Finding the definitive help information for a plugin should be
>>> absolutely trivial and built-in; having the CLI option which give the
>>> code-you-are-executing-right-now the ability to answer that question
>>> avoids the issues we have toda
On 5-Feb-08, at 7:44 AM, Max Bowsher wrote:
Jason van Zyl wrote:
On 4-Feb-08, at 4:20 PM, Dan Fabulich wrote:
Jason van Zyl wrote:
I'm not saying the CLI is a good option. I think it's a bad
option. Keep this out of the core. It's perfectly fine as a plugin.
I'll throw in my two cents an
Jason van Zyl wrote:
On 4-Feb-08, at 4:20 PM, Dan Fabulich wrote:
Jason van Zyl wrote:
I'm not saying the CLI is a good option. I think it's a bad option.
Keep this out of the core. It's perfectly fine as a plugin.
I'll throw in my two cents and point out that while I basically agree
with
On Feb 4, 2008, at 8:49 PM, Dan Fabulich wrote:
Tim O'Brien wrote:
I'm sorry, hold on... starting stopwatch "mvn help:describe -
Dplugin=nifty -Dmojo=nifty -Dfull" - alright, I type fast, but that
took me 10 seconds. Then I hit enter and a whole *crapload* of
information zoomed past
Tim O'Brien wrote:
I'm sorry, hold on... starting stopwatch "mvn help:describe
-Dplugin=nifty -Dmojo=nifty -Dfull" - alright, I type fast, but that took me
10 seconds. Then I hit enter and a whole *crapload* of information zoomed
past. Ok, CTRL-R, mvn, adding a "| less". Ok, for some
On Feb 4, 2008 5:14 PM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> Jan Nielsen wrote:
>
> > Finding the definitive help information for a plugin should be
> > absolutely trivial and built-in; having the CLI option which give the
> > code-you-are-executing-right-now the ability to answer that questio
On Feb 4, 2008, at 6:14 PM, Dan Fabulich wrote:
Jan Nielsen wrote:
Finding the definitive help information for a plugin should be
absolutely trivial and built-in; having the CLI option which give
the code-you-are-executing-right-now the ability to answer that
question avoids the issues w
On 4-Feb-08, at 4:20 PM, Dan Fabulich wrote:
Jason van Zyl wrote:
I'm not saying the CLI is a good option. I think it's a bad option.
Keep this out of the core. It's perfectly fine as a plugin.
I'll throw in my two cents and point out that while I basically
agree with this, I don't think
Jason van Zyl wrote:
I'm not saying the CLI is a good option. I think it's a bad option. Keep this
out of the core. It's perfectly fine as a plugin.
I'll throw in my two cents and point out that while I basically agree with
this, I don't think the help plugin is adequately documented by the
Jan Nielsen wrote:
Finding the definitive help information for a plugin should be
absolutely trivial and built-in; having the CLI option which give the
code-you-are-executing-right-now the ability to answer that question
avoids the issues we have today with multiple sources for a plugin with
On 4-Feb-08, at 3:37 PM, Jan Nielsen wrote:
FWIW, I (and probably 99.9% of the Maven user-base) have desired just
this kind of option for plugins for a l o o o n g time. Something
like:
mvn nifty help
mvn nifty -h
mvn nifty --help
mvn nifty:help
This one is fine. As it doesn't need to
FWIW, I (and probably 99.9% of the Maven user-base) have desired just
this kind of option for plugins for a l o o o n g time. Something
like:
mvn nifty help
mvn nifty -h
mvn nifty --help
mvn nifty:help
mvn nifty:option
mvn nifty
and if you do:
mvn nifty:invalid
you just get the
On 4-Feb-08, at 4:09 AM, Vincent Siveton wrote:
Hi,
2008/2/3, Jason van Zyl <[EMAIL PROTECTED]>:
I think keeping this out of the core, be that the lifecycle executor
or the CLI would be a far better option.
Agree for CLI.
I'm not saying the CLI is a good option. I think it's a bad option
Hi,
2008/2/3, Jason van Zyl <[EMAIL PROTECTED]>:
> I think keeping this out of the core, be that the lifecycle executor
> or the CLI would be a far better option.
Agree for CLI.
> Vincent, just to be clear you have taken the logic that already exists
> in the help plugin?
More wrapped logic fro
Hi,
2008/2/3, Brett Porter <[EMAIL PROTECTED]>:
> Something like
>
> mvn -H idea:idea or mvn -H idea
I didn't think about this kind of CLI option before! It sounds good
for the end user.
> which is akin to what Subversion has, for example.
>
> this would allow the CLI to translate to the appropr
I think keeping this out of the core, be that the lifecycle executor
or the CLI would be a far better option.
Vincent, just to be clear you have taken the logic that already exists
in the help plugin?
On 3-Feb-08, at 3:17 PM, Brett Porter wrote:
Something like
mvn -H idea:idea or mvn -H
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
Something like
mvn -H idea:idea or mvn -H idea
which is akin to what Subversion has, for example.
this would allow the CLI to translate to the appropriate help:describe
goal and then exit, which is pretty clean, as compared to modifying
the lifecycle executor.
- Brett
On 04/02/2008, at 1
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 intuitiv
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.
Back
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/p
22 matches
Mail list logo
