【Maven】Unknown lifecycle phase "build"
2017-04-18 11:09
603 查看
今天对项目打个war包,先执行mvn clean build 突然报错,查了一些原因。
maven提供了解决方案
http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException
This error is generated if you try to invoke a build command that Maven does not understand. In general, you have the following options to perform build steps:
Invoke a lifecycle phase, e.g.
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.
Invoke a plugin goal via the plugin prefix, e.g.
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-defined plugin groups.
Invoke a plugin goal via the versionless plugin coordinates, e.g.
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.
Invoke a plugin goal via the fully qualified plugin coordinates, e.g.
You can freely mix all of these styles within a single command line.
The error described here is usually caused by typo in the command so be sure to check you specified a valid lifecycle phase.
执行上面的四条命令,
[ERROR] Unknown lifecycle phase "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-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] org.apache.maven.lifecycle.LifecyclePhaseNotFoundException: Unknown lifecycle phase "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-clean, clean, post-clean, pre-site, site, post-site, site-deploy. at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateLifecycleMappings(DefaultLifecycleExecutionPlanCalculator.java:228) at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateMojoExecutions(DefaultLifecycleExecutionPlanCalculator.java:199) at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:118) at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.calculateExecutionPlan(DefaultLifecycleExecutionPlanCalculator.java:135) at org.apache.maven.lifecycle.internal.builder.BuilderCommon.resolveBuildPlan(BuilderCommon.java:97) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:109) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216) at org.apache.maven.cli.MavenCli.main(MavenCli.java:160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) [ERROR] [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/LifecyclePhaseNotFoundException
maven提供了解决方案
http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException
This error is generated if you try to invoke a build command that Maven does not understand. In general, you have the following options to perform build steps:
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.
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-defined plugin groups.
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.
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.
The error described here is usually caused by typo in the command so be sure to check you specified a valid lifecycle phase.
执行上面的四条命令,
相关文章推荐
- maven项目构建出现Unknown lifecycle phase "build".提示解决方法
- 我的maven:Unknown lifecycle phase "complile"报错的解决办法
- Maven编译报错 Unknown lifecycle phase "mvn" 解决办法
- maven 系列- Unknown lifecycle phase "mvn".
- Maven编译报错 Unknown lifecycle phase "mvn" 解决办法
- Jar包冲突解决方法 Unknown lifecycle phase "mvn" Eclipse中执行maven命令
- Eclipse集成Maven打包时报错:Unknown lifecycle phase "mvn". You must specify a valid lifecycle phase or a goa
- MAVEN 报错系列--(一) Unknown lifecycle phase "mvn".
- Maven异常_06_ Unknown lifecycle phase "mvn"
- jenkins 构建maven工程--Unknown lifecycle phase "clean"
- 执行第一maven用例出错:Unknown lifecycle phase "omplile".不知如何解决
- Unknown lifecycle phase "mybatis-generator-generate"
- Maven: Build lifecycle and Phases and Goals
- Unknown lifecycle phase "mvn". 报错的解决办法
- 执行第一maven用例出错:Unknown lifecycle phase "complile".
- 错误LifecyclePhaseNotFoundException,Unknown lifecycle phase "mvn". You must specify a valid lifecycle
- 解决在m2eclipse中执行mvn package命令出现的Unknown lifecycle phase "mvn".问题
- Unknown lifecycle phase "mvn". 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>
- 执行第一maven用例出错:Unknown lifecycle phase "complile".
- Unknown lifecycle phase "mvn". You must specify a valid lifecycle phase or a goal