Configuring Maven to Work with Mule ESB
|Mule Runtime Engine versions 3.5, 3.6, and 3.7 reached End of Life on or before January 25, 2020. For more information, contact your Customer Success Manager to determine how you can migrate to the latest Mule version.|
When working with Maven and Mule outside of Anypoint Studio, you need to configure your Maven installation to work successfully with Mule. This page covers how to maintain your POM file to add or adjust dependencies and point to the correct MuleSoft repositories, and how to modify your Maven
settings.xml file to include credentials and profiles for the Enterprise repository.
Once you have modified your Maven installation, you can install Mule plugins and develop applications that reference the Mule open source or Enterprise repositories.
Developing in Maven is greatly simplified by the Maven Tools for Mule ESB plugin, which provides Maven archetypes for building Mule applications.
Note: Anypoint Exchange provides Maven dependency information. Click a connector asset and click Dependency Snippets to list the Maven pom.xml file dependency.
This document assumes that you are working with Maven outside of Anypoint Studio, and thus will be using archetypes to build Mule applications. See Using Maven with Mule for an overview of using Maven to manage your Mule projects.
Note that you generally do not need to modify your settings.xml file if you are working with Maven through Studio, as Studio keeps track of the dependencies you’ll need and attempts to manage them for you in the application’s associated POM file. If dependency errors occur, you may need to manually adjust your POM file, and, in some cases, in your settings.xml. Refer to the Maven documentation for the pom.xml and settings.xml for specific instructions.
Before you can start using Maven to create new Mule projects from the command line using archetypes, you need to:
Ensure that Maven is installed in a directory that does not include spaces.
Create or maintain your already-created
pom.xmlfiles for your applications to include references to the MuleSoft open-source repositories and any connectors, modules, or other extensions that you need to include in each application.
Enterprise users only: Modify the
settings.xmlfile to point to the Enterprise Customer repository and provide your credentials.
By default, your local Maven installation stores configuration files in the directory
~/.m2 on Unix and Mac;
C:\Documents and Settings\<user>\.m2 on Windows). Keep in mind that in Linux or Mac
.m2 is a hidden folder.
If you are building your project outside Studio, you need to manually add some required JARs which cannot be accessed publicly through Maven. In Mule Enterprise Edition, the command line tool
populate_m2_repo, which is available in your
$MULE_HOME/bin directory, can fetch all the associated files. Note: Avoid duplicating jars in your project which causes classloading errors.
Execute one of the following commands:
my-m2-test-repository must not already exist in the current directory.)
Note that you may encounter errors if your
MULE_HOME is set to a path containing spaces. It is recommended that you select a
MULE_HOME location that does not contain spaces.
To enable MuleSoft plugins, you can modify either your project file (POM) or your
settings.xml file. Edit the desired configuration file to include the following:
<settings> <pluginGroups> <pluginGroup>org.mule.tools</pluginGroup> </pluginGroups> ... </settings>
settings.xml or project file to include the following:
<repositories> ... <repository> <id>mulesoft-releases</id> <name>MuleSoft Repository</name> <url>http://repository.mulesoft.org/releases/</url> <layout>default</layout> </repository> <repository> <id>mulesoft-snapshots</id> <name>MuleSoft Snapshot Repository</name> <url>http://repository.mulesoft.org/snapshots/</url> <layout>default</layout> </repository> ... </repositories>
If the dependencies that you need are not already present, add them as shown.
<dependencies> ... <dependency> <groupId>GROUP ID OF DEPENDENCY</groupId> <artifactId>ARTIFACT ID OF DEPENDENCY</artifactId> <version>VERSION OF DEPENDENCY</version> </dependency> ... <dependencies>
For example, if you were adding the dependency for the Salesforce connector:
<dependencies> ... <dependency> <groupId>org.mule.modules</groupId> <artifactId>mule-module-sfdc</artifactId> <version>LATEST</version> </dependency> ... <dependencies>
Not sure what the dependency details are for a connector that you need? Refer to the connector-specific Maven instructions on the connectors site.
This section assumes that you have acquired an Enterprise License and credentials for the MuleSoft Enterprise Maven customer repository, which allows you to access Mule Enterprise modules, connectors, and other components not included in the trial or community versions. If you are a MuleSoft customer and do not have access to the repository, contact MuleSoft Support.
To configure Maven to access the MuleSoft Customer Repository, you need to make additions to the
settings.xml config file. Your
.m2 directory may already contain a configuration file called
settings.xml. Note that this file is not mandatory; Maven uses default parameters if the file is not present. If you don’t have a
settings.xml file at all, create it inside the
~/.m2 folder. Read more about the
settings.xml file in the Maven documentation.
Open the file
Add the following to the
<server> <id>MuleRepository</id> <username>YOUR_ID</username> <password>YOUR_PASSWORD</password> </server>
Add the following to the
<profile> <id>Mule</id> <activation> <activeByDefault>true</activeByDefault> </activation> <repositories> <repository> <id>MuleRepository</id> <name>MuleRepository</name> <url>https://repository.mulesoft.org/nexus-ee/content/repositories/releases-ee/</url> <layout>default</layout> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </repository> </repositories> </profile>