maven NoGoalSpecifiedException

转（http://tom.grade1986.blog.163.com/blog/static/36033556201241514731684/）

异常信息：

[INFO] Scanning for projects…[INFO]
[INFO] BUILD FAILURE[INFO]
[INFO] Total time: 0.109s[INFO] Finished at: Wed Apr 13 11:04:20 CST 2011[INFO] Final Memory: 1M/4M[INFO]
ERROR] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources,
process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-
test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-site, site, post-site, site-deploy,
pre-clean, clean, post-clean. -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException 

resolution：打开-X参数 mvn -X

reference:https://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException

Well, this just tells you that Maven has no idea what it should do. In general, you have the following options to perform build steps:

1. Invoke a lifecycle phase, e.g.

   mvn install 

   This runs the lifecycle phase install and all its predecessor phases like compile and test. Please see Introduction to the Build Lifecycle for more information about available lifecycle phases.

2. Invoke a plugin goal via the plugin prefix, e.g.

   mvn compiler:compile 

   Eventually, the plugin prefix translates to a group id and artifact id of a plugin. Maven resolves plugin prefixes by first looking at the plugins of the current project's POM and next by checking the metadata of user-definedplugin groups.

3. Invoke a plugin goal via the versionless plugin coordinates, e.g.

   mvn org.apache.maven.plugins:maven-compiler-plugin:compile 

   To resolve the plugin version, Maven will first check the project's POM and fallback to the latest release version of the plugin that was deployed to the configured plugin repositories.

4. Invoke a plugin goal via the fully qualified plugin coordinates, e.g.

   mvn org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile 

You can freely mix all of these styles within a single command line but you have to specify at least one goal/phase to get Maven going. Alternatively, you can define a default goal in your POM as shown below:

<project>   ...   <build>     <defaultGoal>install</defaultGoal>     ...   </build>   ... </project>