Tempted to go ahead and write your own plugin ? No obligation, but you might want to share it with the Sonar community. In that case hosting your plugin at sonar-plugins.codehaus.org brings you many benefits :
- the community helps you more easily, as well as the community benefits from the plugin
- free hosting in the subversion repository
- use JIRA to track issues
- use Atlassian Bamboo for continuous integration
- use this wiki for the documentation
- the plugin is automatically shown in the update center (feature to come soon), so users can install the plugin directly from the application
- Create an account at Codehaus
- Subscribe to firstname.lastname@example.org
- Send e-mail to email@example.com and tell us your Codehaus ID, so that we can give you a commit access to subversion. You can request access rights to Nemo too.
When you utilize the forge, we request that you respect the following principles :
- A plugin is built with Maven
- You should follow Best practices and Sonar Code Style.
- The copyright belongs to whoever wrote the plugin
- The license should be business friendly
- The directory name is the plugin name. Maven groupId is 'org.codehaus.sonar-plugins' and artifactId is 'sonar-<name>-plugin'. For example the plugin "foo" is stored in the directory "foo" and its artifact id is "sonar-foo-plugin"
- Set the following properties :
- Configure your pom by overriding values provided by parent - see Sonar Plugins Forge Parent POM. Default license is LGPL3.
- Follow Maven POM Code Convention
- Add the plugin to the main pom of the forge
Send an email to the dev mailing list in order the plugin to be added to our Continuous Integration server.
How to release
How to release a plugin version is explained in this page.