Sharing Custom Code
|MuleSoft recommends against deployments to Mule 3.8. Standard Support for this version ended on November 16, 2018, and Mule 3.8 will reach its End of Life on November 16, 2021, when Extended Support ends.|
Besides all the common code that exists in a company, there are Mule specific programmatic artifacts that are worth considering sharing.
Let’s name a few:
The most convenient way to share custom code across team is to rely on Maven’s dependency management mechanism. Here is an extract of a pom.xml referring to common code stored in a shared Maven library:
<dependency> <groupId>com.acme.mulings</groupId> <artifactId>common-mule-project</artifactId> <version>1.3</version> </dependency>
The Mule build plug-in will automatically bundle these extra dependencies in the /lib directory of the deployable application. In this case, the common-mule-project-1.3.jar will be added to this directory at build time, ready to be deployed and made available to the application running on Mule.