Tempted to write your own plugin? Want to contribute your plugin back to the community? If you do, we'd be happy to host your FOSS plugins in the SonarSource plugin forge. After all, it gives you a broader audience and enhances the community. Everyone’s a winner. Plus:
If you're not interested in writing your own plugin, but just want to see what's currently being hammered into shape in the forge, check out the plugins under development.
To keep your plugin in the forge, it must remain in compliance with everything on the first list and:
be maintained over time (meaning you should pay attention to the mailing lists and respond to bugs and API changes)
preferably receive at least one +1 from a voting member of the development mailing list for subsequent releases (although passing a vote by lazy consensus is allowed.)
If any of these requirements are not met, or stop being met (if, for example you change the license to one that’s not business-friendly) we may remove the plugin from the forge immediately
When the plugin is approved, send your Codehaus ID to firstname.lastname@example.org and we'll give you a commit access to github.
sonar-<name>-plugin. For example the plugin "foo" is stored in the directory foo and its artifact id is
Set the following properties:
<project> <parent> <groupId>org.codehaus.sonar-plugins</groupId> <artifactId>parent</artifactId> <!-- The latest version can be found by looking at http://search.maven.org/#search|gav|1|g%3A%22org.codehaus.sonar-plugins%22%20AND%20a%3A%22parent%22 --> <version>REPLACE_BY_LATEST_VERSION</version> </parent> <artifactId>sonar-foo-plugin</artifactId> <version>1.0-SNAPSHOT</version> <packaging>sonar-plugin</packaging> <name>Plugin name</name> <description>Plugin description</description> <url>http://docs.codehaus.org/display/SONAR/MY+PLUGIN</url> <inceptionYear>2014</inceptionYear> <organization> <name>My Organization</name> <url>http://www.my-organization.com</url> </organization> <issueManagement> <system>JIRA</system> <url>http://jira.codehaus.org/browse/SONARPLUGINS/component/MY-JIRA-COMPONENT-ID</url> </issueManagement> <scm> <connection>scm:git:email@example.com:SonarCommunity/MY-PLUGIN.git</connection> <developerConnection>scm:git:firstname.lastname@example.org:SonarCommunity/MY-PLUGIN.git</developerConnection> <url>https://github.com/SonarCommunity/MY-PLUGIN</url> <tag>HEAD</tag> </scm> ... </project>
Send an email to email@example.com, so we can register the plugin at Cloudbees.
The following configuration of code style must be applied.
The release process is detailed on this page.