Runs Maven operations on a Maven project folder. It is possible to configure the plugin to use external Maven installs and to setup environment variables for use be by the plugin operation.
Target Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
Maven Home |
| No | If it is desired to use an external Maven, fill in the Maven Home up to but not including the bin folder here. Otherwise, the internal Maven 3.05 will be used. (e.g. The folder should have a bin folder inside it with the maven executable |
Maven Environment Script |
| No | If necessary, provide a script to source variables for use by the Maven Plugin. This script can refer to other scripts, (e.g. . or if you don't have a script to run, you can export directly (e.g. |
Inputs
Input Name | Input Code | Required | Description |
---|---|---|---|
Project Location |
| No | Path to the project which contains a POM file. If a relative path is given, a path inside In older versions of the plugin, it had been required. Please upgrade to the latest plugin version. |
Run Phases |
| Yes | Space-delimited Maven life cycle phases to execute (e.g. |
Arguments |
| No | Space-delimited argument list (e.g. |
Save Artifacts |
| No | If checked, artifacts will be saved to the Artifacts folder automatically. Otherwise, you may want to place a saveArtifacts step after this. All files present directly in the subfolder location are copied if checked. |
Artifacts Subfolder |
| No | Subfolder inside the Project Location where artifacts are generated by Maven. Defaults to "target" If your artifacts need to come from another location, specify it instead. |
...
This operation produces artifacts if the FDMVN_INP_ARTIFACTS_SUBFOLDER option is checked. Otherwise, you may wish to use the file plugin to move the correct files to the artifacts folder later in the workflow.
...