The buildMule operation allows for building Mule projects, whether they are Maven projects or not.
The plugin's versatility allows for use in a number of different scenarios.
...
| Maven Projects | Non-Maven Projects |
|---|---|
If a pom.xml is found in the |
...
projectPath, it will be run with Maven, using |
...
the |
...
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. |
...
If |
...
the project is not a Maven project, it will be built using javac and other command line tools. Make sure that the Java_HOME specified on the endpoint is a JDK of the required version. The |
Environment/Instance Properties
...
Property Name | Property Code | Required | Description |
|---|---|---|---|
FDMULE_APP_NAME | |||
FDMULE_HOME | If it is not a Maven Project. |
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| 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 |
...