Managing and maintaining the source projects in large scale Mulesoft API environments can evolve to a near impossible task, but leveraging the full possibilities of a build tool like maven will significantly ease the burden. I am fully aware that my example comes nowhere near a real life situation. To make it up to you, keep an eye on the blog, in my next post on parent POMs I will cover a POM inheritance model with multiple layers and different parents for various types of mule APIs / batch projects. I hope you have enjoyed reading this post. Any comments and remarks are more than welcome.
Sources used for this post:
Mulesoft and maven: https://docs.mulesoft.com/mule-user-guide/v/3.9/using-maven-with-mule
Mulesoft shared resources: https://docs.mulesoft.com/mule-user-guide/v/3.9/shared-resources#deploying-with-shared-resources
Maven parent POMs: https://maven.apache.org/pom/index.html
Maven dependency management: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
Maven integration for eclipse: http://www.eclipse.org/m2e/