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
different HTML usage information.
Have you tried "mvn help:describe -Dplugin=nifty -Dmojo=nifty -Dfull"? I
think we already have what you want, but we've yet again failed to
document it adequately. (Try it with -Dplugin=compiler -Dmojo=compile.)
And while I'm at it, and relatedly, whatever happened to "-G" to get me
a list of all plugins???
I never used 1.x, but I don't think that makes sense any more. We could
certainly provide a list of all valid lifecycle phases (and we should do
so in the help plugin), since those are static and don't change.
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
But as for finding plugins, it's better to search the Internet for that
sort of thing, rather than trying to turn the Maven core into an Internet
search engine for Maven plugins. (Similarly, wouldn't it be cool if you
could use a simple Maven command-line switch to search for jars you could
use in your project? Wait, no it wouldn't; that's what Google is for.)
And I might as well chuck in: why in the world do I need to do "mvn
nifty:nifty" and not just "mvn nifty"?
Because that way we don't have to guess whether you're trying to run a
goal or a lifecycle phase. "install" is a great example. Do you just
want to run the install:install goal, or did you want to run every
lifecycle phase up through the install phase?
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
