build-helper:attach-artifact
Full name:
org.codehaus.mojo:build-helper-maven-plugin:3.6.0:attach-artifact
Description:
Attach additional artifacts to be installed and deployed.
Attributes:
- Requires a Maven project to be executed.
- The goal is thread-safe and supports parallel builds.
- Since version:
1.0. - Binds by default to the lifecycle phase:
package.
Required Parameters
| Name | Type | Since | Description |
|---|---|---|---|
<artifacts> |
Artifact[] |
- |
Attach an array of artifacts to the project. |
Optional Parameters
| Name | Type | Since | Description |
|---|---|---|---|
<runOnlyAtExecutionRoot> |
boolean |
1.5 |
This will cause the execution to be run only at the top of a given module tree. That is, run in the project contained in the same folder where the mvn execution was launched. Default: falseUser Property: buildhelper.runOnlyAtExecutionRoot |
<skipAttach> |
boolean |
1.6 |
This allows to skip the attach execution in case it is known that the corresponding file does not exists. For example, when the previous ant-run task is skipped with a unless. Default: falseUser Property: buildhelper.skipAttach |
Parameter Details
<artifacts>
Attach an array of artifacts to the project.
- Type:
org.codehaus.mojo.buildhelper.Artifact[] - Required:
Yes
<runOnlyAtExecutionRoot>
This will cause the execution to be run only at the top of a given module tree. That is, run in the project contained in the same folder where the mvn execution was launched.
- Type:
boolean - Since:
1.5 - Required:
No - User Property:
buildhelper.runOnlyAtExecutionRoot - Default:
false
<skipAttach>
This allows to skip the attach execution in case it is known that the corresponding file does not exists. For example, when the previous ant-run task is skipped with a unless.
- Type:
boolean - Since:
1.6 - Required:
No - User Property:
buildhelper.skipAttach - Default:
false