If a pom.xml is found in the projectPath, it will be run with Maven, using the package lifecycle. Any tests will be run during the build process. The output of the tests will be in the plugin execution log.

If more control over the lifecycles or arguments is required, the runMaven operation works exactly the same, except that it doesn’t save the artifact to the artifact repository automatically. This can be done with the File - saveArtifacts operation.

This operation should run on the Mule server where the project will be deployed. This allows the project’s build to be a more complete test of the environment.

If the project is not a Maven project, it will be built using javac and other command line tools.

Make sure that the JDK HOME specified on the endpoint is a JDK of the required version.

The Mule Home (FDMULE_HOME) property is used to find the libraries that are necessary to compile the Mule project.

Mule Home

FDMULE_HOME

If it is not a Maven Project.

Path to a Mule Server Installation

Mule Project Path

FDMULE_PROJECT_PATH

No

This is the folder that typically is named for your application and contains your [src] folder. Relative paths are sourced from the FD_TEMP_DIR.

http.port

FDMULE_HTTP_PORT

No

HTTP port to use when running Maven tests. This should be a different number than the one that is usually used to run the application on the server. This only works if ${http.port} is used in your HTTP Connector.

Additional Maven Arguments

FDMULE_MVN_ARGS

No

Space-delimited list of additional Maven arguments (e.g. -e -X)