Your new maven friend – the mule maven

1. Your new Maven friend – the
Mule Maven Plugin 2.0

2. • If you’re a Mule user, there’s a good chance that you’re using Maven
to automate building and testing of your applications. We’re happy to
announce Mule Maven Plugin 2.0, to help you automate your
deployment and integration tests. This plugin will help you no matter
where do you want it to run: CloudHub, a local Standalone server,
Anypoint Runtime Manager, a local cluster or using the Mule Agent.

3. Continuous deployment and integration tests are a
core part of software development best practices.
And many of our customers are using Maven to
help achieve those. The new version of our Maven
plugins makes these pratices simple for Maven
users. It can:
• Deploy and undeploy applications to different Mule environments
• It supports Mule Standalone, Mule Cluster, Anypoint Runtime Manager,
CloudHub, and the Mule Agent
• It supports attaching to different lifecycle stages of Maven so you can use the
plugin for both integration tests and continuous deployment.
• You can use the plugin with both Community and Enterprise Mule instances

4. Getting Started
• You can see several examples in the documentation, but here’s quick guide
on how to get started. First, you need to add MuleSoft’s releases repository
to your pom.xm or settings.xml so Maven can find the plugin:
<pluginRepositories>
<pluginRepository>
<id>mule-public</id>
<url>https://repository.mulesoft.org/nexus/content/repositories/releases</
url>
</pluginRepository>
</pluginRepositories>

5. • We recommend to use mule-app-maven-plugin for packaging your
Mule application. This way, the mule-maven-plugin will automatically
pick the packaged Mule application and deploy it. Then, if you want
to deploy the result of your build to CloudHub for example, add this
to your Maven plugins section:

6. <plugin>
<groupId>org.mule.tools.maven</groupId>
<artifactId>mule-app-maven-plugin</artifactId>
<version>1.1</version>
<extensions>true</extensions>
</plugin>
<plugin>
<groupId>org.mule.tools.maven</groupId>
<artifactId>mule-maven-plugin</artifactId>
<version>2.0</version>
<configuration>
<deploymentType>cloudhub</deploymentType>
<muleVersion>3.7.0</muleVersion>
<username>myUsername</username>
<password>myPassword</password>
<redeploy>true</redeploy>
<environment>Production</environment>
</configuration>
<executions>
<execution>
<id>deploy</id>
<phase>deploy</phase>
<goals>
<goal>deploy</goal>
</goals>
</execution>
</executions>
</plugin>

7. • A different use case is to run integration tests in a local Mule
Standalone server, before deploying to qa or prod environments.
Using both maven-failsafe-plugin and mule-maven-plugin gives you a
simple and efficient way to do so:

8. <plugins>
<plugin>
<groupId>org.mule.tools.maven</groupId>
<artifactId>mule-app-maven-plugin</artifactId>
<version>1.1</version>
<extensions>true</extensions>
</plugin>
<plugin>
<groupId>org.mule.tools.maven</groupId>
<artifactId>mule-maven-plugin</artifactId>
<version>2.0</version>
<configuration>
<deploymentType>standalone</deploymentType>
<muleVersion>3.7.0</muleVersion>
</configuration>
<executions>
<execution>
<id>deploy</id>
<phase>pre-integration-test</phase>
<goals>
<goal>deploy</goal>
</goals>
</execution>
<execution>
<id>undeploy</id>
<phase>post-integration-test</phase>
<goals>
<goal>undeploy</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>

9. • In this case the plugin will download the Mule distribution from a Maven
repository (or use one that’s already installed), start the server during pre-
integration-tests, and stop the server during post-integration-test phase.
You only need to name your test so that it has the suffix “ITCase.java”.
• These are just the basics, but you can also deploy domains, add third party
libraries, deploy external applications, configure deployment arguments,
and even run a custom Groovy script just before deploying. To get started,
check out our documentation, read the release notes or try running one of
the examples available in the documentation and make your build process
a nice one.