Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 60 Next »

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 available in Update Center, so users can install the plugin directly from the application

Request hosting

  1. Create an account at Codehaus
  2. Subscribe to dev@sonar.codehaus.org
  3. Send e-mail to dev@sonar.codehaus.org and tell us your Codehaus ID, so that we can give you a commit access to github. You can request access rights to Nemo too.

Prerequisites

  • The plugin must support Java 5. The Continuous Integration job uses Oracle JDK 1.5.
  • The plugin is built with Maven 2.2.* or 3.*.

Principles

When you utilize the forge, we request that you respect the following principles :

  1. Follow Best practices and Sonar Code Style.
  2. The copyright belongs to whoever wrote the plugin
  3. The license must be business friendly
  4. Follow the release process described bellow.

Maven POM

  • The directory name is the plugin name.
  • The 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 :

    pom.xml
  • 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

Continuous Integration

Please send an email to the dev mailing list in order the plugin to be added to our Continuous Integration server.

How to Release

The release process is explained in this page.

  • No labels