細(xì)心是最珍貴的品質(zhì)。
先看一段命令的輸出
sunyelw@windows:eureka_consume$
sunyelw@windows:eureka_consume$ mvn clean
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building eureka_consume V1.5.7
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ eureka_consume ---
[INFO] Deleting C:\idea\workspace\cloud\eureka_consume\target
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.132 s
[INFO] Finished at: 2020-04-12T11:12:49+08:00
[INFO] Final Memory: 14M/155M
[INFO] ------------------------------------------------------------------------
sunyelw@windows:eureka_consume$
這段輸出中就看一行
[INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ eureka_consume ---
前面的maven-clean-plugin:2.6.1:clean是插件及具體執(zhí)行目標(biāo),最后的eureka_consume是服務(wù)名,請(qǐng)問中間的default-clean 是什么?
我們知道m(xù)aven的生命周期有三個(gè), clean,default,site。maven只是制定了一套代碼處理流程,并不負(fù)責(zé)具體實(shí)現(xiàn),具體實(shí)現(xiàn)交由插件的目標(biāo)來完成,這點(diǎn)就不再贅述了(可以看下之前的maven系列文件)
而mvn命令有兩種執(zhí)行方式
- 基于phase,比如 clean、package、test等
- 基于goal,需要指定插件版本與具體目標(biāo),舉例
sunyelw@windows:eureka_consume$ mvn org.apache.maven.plugins:maven-clean-plugin:2.6.1:clean
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building eureka_consume V1.5.7
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.6.1:clean (default-cli) @ eureka_consume ---
[INFO] Deleting C:\idea\workspace\cloud\eureka_consume\target
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.444 s
[INFO] Finished at: 2020-04-12T11:29:25+08:00
[INFO] Final Memory: 11M/155M
[INFO] ------------------------------------------------------------------------
sunyelw@windows:eureka_consume$
很明顯,我們執(zhí)行的是基于phase(階段),然后clean生命周期的clean 階段綁定了 clean插件的clean目標(biāo)
那么回到開頭的那個(gè)問題,default-clean 是不是表示default生命周期?
如果你沒有自己定義過任何插件,那么你看到的執(zhí)行目標(biāo)都是以 default 開頭的,這里的default并不是指default生命周期,而是mave官方默認(rèn)綁定的。
我們加個(gè)我們自己定義的插件
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
</plugin>
<plugin>
<groupId>com.sun.yelw</groupId>
<artifactId>hy-maven-plugin</artifactId>
<version>3.5.1</version>
<executions>
<execution>
<id>diy-1</id>
<phase>pre-clean</phase>
<goals>
<goal>hy-an</goal>
</goals>
</execution>
<execution>
<id>diy-2</id>
<phase>post-clean</phase>
<goals>
<goal>hy-doc</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
- 當(dāng)有多個(gè)execution時(shí),必須指定execution-id,這里分為diy-1和diy-2
- 插件 hy-maven-plugin 中有兩個(gè)目標(biāo) hy-an、hy-doc,分別表示自定義插件的兩種方式:@Mojo和文件注釋
- 分別綁定到 pre-clean 和 post-clean
接下來再執(zhí)行一下,這里為了執(zhí)行到post-clean就直接執(zhí)行post-clean了
sunyelw@windows:eureka_consume$ mvn post-clean
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building eureka_consume V1.5.7
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- hy-maven-plugin:3.5.1:hy-an (diy-1) @ eureka_consume ---
[ERROR] ++++++++++++++++++++
[ERROR] hy-plugin-execute-by-annotation
[ERROR] ++++++++++++++++++++
[INFO]
[INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ eureka_consume ---
[INFO] Deleting C:\idea\workspace\cloud\eureka_consume\target
[INFO]
[INFO] --- hy-maven-plugin:3.5.1:hy-doc (diy-2) @ eureka_consume ---
[ERROR] ++++++++++++++++++++
[ERROR] hy-plugin-execute-by-document
[ERROR] ++++++++++++++++++++
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.036 s
[INFO] Finished at: 2020-04-12T11:37:50+08:00
[INFO] Final Memory: 14M/155M
[INFO] ------------------------------------------------------------------------
sunyelw@windows:eureka_consume$
執(zhí)行順序
- diy-1
- default-clean
- diy-2
所以這個(gè) default-clean 是 execution-id,那么在哪定義的呢?
我們先看下 clean 插件的clean目標(biāo) CleanMojo.java代碼地址
@Mojo( name = "clean", threadSafe = true )
public class CleanMojo
extends AbstractMojo
{
...
}
這里我們只看到了一個(gè)clean名稱,并沒有看到 default-clean 字段。
其實(shí)上面我們發(fā)現(xiàn)這個(gè) execution-id 是定義在添加插件里面的,而這個(gè)是maven官方添加的,當(dāng)然需要去看下其源碼實(shí)現(xiàn) maven源碼
拉下來
git clone --depth 1 git@github.com:apache/maven.git
找下有沒有 default 或 default- 開頭的代碼
sunyelw@windows:maven$ grep 'default-' * -Rn > default_.md
sunyelw@windows:maven$ grep 'goal' default_.md
maven-compat/src/test/java/org/apache/maven/project/EmptyLifecycleExecutor.java:93: pluginExecution.setId( "default-" + goal );
maven-compat/src/test/java/org/apache/maven/project/EmptyLifecyclePluginAnalyzer.java:70: pluginExecution.setId( "default-" + goal );
maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecyclePluginAnalyzer.java:256: String base = "default-" + goal;
maven-core/src/test/java/org/apache/maven/lifecycle/EmptyLifecyclePluginAnalyzer.java:69: pluginExecution.setId( "default-" + goal );
maven-core/src/test/java/org/apache/maven/lifecycle/internal/stub/LifeCyclePluginAnalyzerStub.java:66: pluginExecution.setId( "default-" + goal );
maven-core/src/test/java/org/apache/maven/project/EmptyLifecycleExecutor.java:92: pluginExecution.setId( "default-" + goal );
sunyelw@windows:maven$
然后在輸出中,排除test目錄下的,還真找到一行
maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecyclePluginAnalyzer.java:256: String base = "default-" + goal;
這就有點(diǎn)激動(dòng)了,打開這個(gè)文件看看

繼續(xù)看下這個(gè)方法調(diào)用

所以execution-id是在這里塞進(jìn)去的,default就是其字面意思,總算弄明白了。
這篇文章就跟到這里了,后面有需要再跟下這個(gè)源碼
又帶著復(fù)習(xí)了一遍maven,感覺一上午啥也沒做。。