Extending Confluence - Atlassian Confluence 5 Essentials - page 286

Releasing your plugin
At a certain point, you are done developing your plugin and you want to deliver the
end result to your company or maybe even to the rest of world. The first thing we
have to do is release your plugin.

The release process relies heavily on you to have a revision control system for your
plugin, like Subversion or GIT. If you don't have such a system in place, you could
consider taking a look at http://bitbucket.org , which is an online Atlassian tool
that offers free source hosting.

Before we can release our plugin, we have to make sure that our pom.xml file has all
the requirements to do so.

To set the SCM properties, perform the following steps:

1. Open the pom.xml file in your plugin.
2. Add the following lines to the file with your SCM information:
<scm>
<connection>
scm:git:[e-mail]:stefankohler/plugin-example-button.git
</connection>
<developerConnection>
scm:git:file:///${basedir}
</developerConnection>
url>
https://bitbucket.org/stefankohler/plugin-example-button
</url>
</scm>

3. Save the pom.xml file.

The connection and developerConnection tell Maven how to connect to your
repository. While connection requires read access for Maven to be able to find the
source code (for example, an update), developerConnection requires a connection
that will give write access.

The url element is not required, but can be used for a publicly accessible URL
to your repository.