No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in t

最新推荐文章于 2023-12-13 18:24:27 发布

ispotu

最新推荐文章于 2023-12-13 18:24:27 发布

阅读量3.5k

点赞数

分类专栏：异常文章标签：异常

异常专栏收录该内容

3 篇文章

订阅专栏

本文详细介绍了使用Maven执行构建任务的各种方式，包括通过生命周期阶段、插件目标、版本无关和完全限定插件坐标来调用不同的构建步骤。此外，还展示了如何在POM文件中定义默认目标。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

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:

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-definedplugin 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 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>