The Maven plugin provides a means to run Maven operations on a maven project.

Supported Versions

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.

Key Features

• Use existing Maven POMs
• Maven is bundled in the plugin, so no need to install Maven on endpoints.
• As of version 4.5.1.2, external Maven executions return test results back to FlexDeploy for use by Test Definitions.

Plugin Operations

• runMaven

Configuration

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.

Special Considerations

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.

• 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 the Arguments input of the workflow operation.
  

  -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.