maven 打包源代码 jar 与 jar-no-fork

淡淡的烟草味﹌ 2021-06-24 14:36 573阅读 0赞

官方解释：

### Goals Overview ###

The Source Plugin has five goals:

*  [source:aggregate][source_aggregate] aggregrates sources for all modules in an aggregator project.
 *  [source:jar][source_jar] is used to bundle the main sources of the project into a jar archive.
 *  [source:test-jar][source_test-jar] on the other hand, is used to bundle the test sources of the project into a jar archive.
 *  [source:jar-no-fork][source_jar-no-fork] is similar to **jar** but does not fork the build lifecycle.
 *  [source:test-jar-no-fork][source_test-jar-no-fork] is similar to **test-jar** but does not fork the build lifecycle.

前言

maven"内置插件"中没有打包源代码的插件，所以，需要开发者配置插件。apache提供了maven-source-plugin插件用于打包源代码。

maven-source-plugin

The Source Plugin has five goals:

*  [source:aggregate][source_aggregate] aggregrates sources for all modules in an aggregator project.
 *  [source:jar][source_jar] is used to bundle the main sources of the project into a jar archive.
 *  [source:test-jar][source_test-jar] on the other hand, is used to bundle the test sources of the project into a jar archive.
 *  [source:jar-no-fork][source_jar-no-fork] is similar to jar but does not fork the build lifecycle.
 *  [source:test-jar-no-fork][source_test-jar-no-fork] is similar to test-jar but does not fork the build lifecycle

配置

在《maven实战》一书中，配置使用的是jar-no-fork

<plugins>
    			<plugin>
    				<artifactId>maven-source-plugin</artifactId>
    				<version>2.1.1</version>
    				
    				<executions>
    					<execution>
    						<id>attach-sources</id>
    						<phase>verify</phase>
    						<goals>
    							<goal>jar-no-fork</goal>
    						</goals>
    					</execution>
    				</executions>
    			</plugin>
    		</plugins>

jar-no-fork与jar的区别

jar，在执行goal之前，执行generate-sources阶段，也就是说，如果，jar绑定的目标在generate-sources之后(比如verify)的话，generate-sources会执行两遍。

*  The goal is thread-safe and supports parallel builds.
 *  Binds by default to the [lifecycle phase][]: package

*  Invokes the execution of the [lifecycle phase][] generate-sources prior to executing itself.

jar-no-fork，没有其余动作，在绑定的phase执行。原文是，

*  The goal is thread-safe and supports parallel builds.

*  Binds by default to the [lifecycle phase][]: package.

为什么会有jar-no-fork?

临时，我也没找到它存在的理由。

参考

[maven-source-plugin doc][]

[difference between maven-source-plugin-jar-and-jar-no-fork-goal][]

[source_aggregate]: http://maven.apache.org/plugins/maven-source-plugin/aggregate-mojo.html
[source_jar]: http://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html
[source_test-jar]: http://maven.apache.org/plugins/maven-source-plugin/test-jar-mojo.html
[source_jar-no-fork]: http://maven.apache.org/plugins/maven-source-plugin/jar-no-fork-mojo.html
[source_test-jar-no-fork]: http://maven.apache.org/plugins/maven-source-plugin/test-jar-no-fork-mojo.html
[lifecycle phase]: http://maven.apache.org/ref/current/maven-core/lifecycles.html
[maven-source-plugin doc]: http://maven.apache.org/plugins/maven-source-plugin/
[difference between maven-source-plugin-jar-and-jar-no-fork-goal]: http://stackoverflow.com/questions/10567551/difference-between-maven-source-plugin-jar-and-jar-no-fork-goal