Runs Maven operations on a Maven project folder.
...
Property Name | Property Code | Required | Description |
---|---|---|---|
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 | FDMVN_INP_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 | FDMVN_INP_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. |
Outputs
Output Name | Required | Description |
---|---|---|
Artifacts
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.
...
This operation delegates endpoint execution to the workflow developer. The workflow editor will default to "Any", which will execute on any one of the selected endpoints, which will be randomly picked from selected endpoints or a specific endpoint where previous step may have executed. Changing this value to "All" to will result in execution on all selected endpoints.
Special Considerations
As of June 2018, the insecure TLS 1.0 & 1.1 protocols are no longer supported for SSL connections to Maven Central.
- If your endpoint is using HTTP to access Central, or Java 8+ with HTTPS URLs, you are not affected.
If your endpoint is running Java 7, it supports TLS 1.2 butit is disabled by defaultin versions before
1.7.0_131-b31
. An easy workaround is to add this code to theArguments
input of the workflow operation.Code Block -Dhttps.protocols=TLSv1.2
- If your endpoint is on Java 6, you will need to switch back to HTTP or upgrade to a more modern Java version.