Maven does have a "help option". It just doesn't list the lifecycles etc that Wendy mentioned. Instead I'd suggest that those responsible for the source code include a README that instructs users where to acquire Maven, what version they require, and what command to run to properly build and package the code.
Once you've used Maven for a project or two, you *know* all the lifecycles, and you know to run "mvn package" or test, install, deploy etc depending on what you're looking to do with it. C:\cvs_root>mvn -h usage: mvn [options] [<goal(s)>] [<phase(s)>] Options: -C,--strict-checksums Fail the build if checksums don't match -c,--lax-checksums Warn if checksums don't match (etc) Wayne On 10/29/06, 向秦贤 <[EMAIL PROTECTED]> wrote:
Hi, Thanks hint. Althrough I'm a newbie to maven, I'd to insist on this help option, just like maven scanning. Supposed that a man get a project code, his first work is just to build, and build what, can build what, he thinks, but maven cannot answer. Isn't it? Regards, Qinxian 在06-10-30，Wendy Smoak <[EMAIL PROTECTED]> 写道： > > On 10/29/06, 向秦贤 <[EMAIL PROTECTED]> wrote: > > > After checked out MavenCli code and found not projecthelp style option, > I > > supposed there is no one. > > If this, I wanna know all if need a mvn help option like ant > -projecthelp. > > Maybe there could have a option, listGoals listTasks or projecthelp. > > For the most part, the 'goals' are the lifecycle phases, and they are > the same for every project. > > > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > > There is also a help plugin that can help you figure out what profiles > are active and what the pom looks like after all the inheritance is > taken into account. The 'describe' goal should work on plugins, > though I wasn't able to get it to do anything useful in my brief > experiments. > > http://maven.apache.org/plugins/maven-help-plugin/ > > -- > Wendy > -- 向秦贤
