Extending Mule: How to a release a new version of your custom extension

November 1 2012

1 comment. 0
motif

Today I would like to talk a little bit about releasing a new version of your Mule extensions.  As you may know Mule is a an extensible platform with well defined integration points for plugging in your own connectors transformations, components and even routers. Suppose you have used The Mule Devkit to create your very own extension or cloud connector, and your project is so cool that it was accepted on MuleForge.

What happens if you make changes to you project and it moves from version 1.0 to 1.1? We’ll take a very quick look at how to do that in this post.

First, modify your pom.xml to increase your version number. In this case, we’ll go from 1.0 to 1.1:

<groupId>org.mule.modules</groupId>
<artifactId>cool-connector</artifactId>
<version>1.1</version>
<packaging>mule-module</packaging>

    

After pushing all your changes to GitHub, execute this Maven command to prepare the release. This will create a new tag with version 1.1 and will upgrade your local copy to version 1.2-SNAPSHOT

The last step is to push the tag and execute the deploy goal. The release plugin can do all of this for you with the following command:

And that’s it! The new version has been released! But, oh wait… If your connector has changed then its documentation has most likely changed as well. Let’s regenerate and publish it as well:

Looks like we’re all set now. I hope you find this useful. Looking forward for trying your very own connectors soon!


We'd love to hear your opinion on this post

One Response to “Extending Mule: How to a release a new version of your custom extension”

  1. […] Extending Mule: How to a release a new version of your custom extension […]

    Agree(0)Disagree(0)Comment