The Maven plugin provides a means to run Maven operations on a maven project.
The Maven Plugin ships with Maven version 3.05, the same version bundled with JDeveloper 12c.
- Supports the standard Maven Lifecycle Phases
- Supports Maven arguments
- Supports sourcing a script to set properties before the execution begins.
- Use existing Maven POMs
- Maven is bundled in the plugin, so no need to install Maven on endpoints.
- As of version 184.108.40.206, external Maven executions return test results back to FlexDeploy for use by Test Definitions.
If you need to customize your maven options, you can edit the
~/.m2/settings.xml on the endpoint, just like if you are editing it for a regular maven user. It is important to make the changes on the endpoint, not the FlexDeploy server, and make sure to perform the configuration changes using the same user that FlexDeploy will login as on the endpoint. You can copy the .m2 folder from another machine if that is easier, or install Maven on the endpoint so that it is created for you and then edit it. This is the easiest way to configure Maven to have settings that apply to all future workflows. The same configuration options can likely be added into the
Arguments plugin input, but would need to be entered each time that a new workflow with Maven in it is created.
As of June 2018, the insecure TLS 1.0 & 1.1 protocols are no longer supported for SSL connections to Maven Central. Click here to read more about this change.