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 10 Next »

Authors

Mike R. Haller (http://www.mhaller.de), Simon Brandhof (SonarSource)

JIRA

http://jira.codehaus.org/browse/SONARPLUGINS/component/13867

Most Recent Version

0.2-SNAPSHOT (check version compatibility )

State

Under development

License

LGPL v3

Sources

http://svn.codehaus.org/sonar-plugins/trunk/clirr/

Download

sonar-clirr-plugin-0.2-SNAPSHOT.jar

Continuous Build

http://bamboo.ci.codehaus.org/browse/SONAR-CLIRR

Features

Clirr checks Java libraries for binary and source compatibility with older releases. In a continuous integration process Clirr can automatically prevent accidental introduction of binary or source compatibility problems.

This Sonar plugin measures the number of API break violations between the current sources and the last known stable version of the library in the Maven repository.

Usage & Installation

  1. Stop Sonar Web server
  2. Copy the JAR file into the /extensions/plugins directory
  3. Restart Sonar Server
  4. Enable Clirr plugin in Project > Settings > Clirr by setting [sonar.clirr.execute property to true
  5. Enable the following three violation rules in your Quality Profile (Configuration > Quality Profiles).
    • API Change adds new feature without breaking anything
    • API Change breaks the backward binary compatibility
    • API Change might change runtime expected behavior
  6. Run mvn sonar:sonar on your Maven project
  7. Go to Sonar Dashboard and look at "API Changes" section

Known limitations

  1. As Clirr does not report line numbers, violations cannot be displayed in the correct location within the source code
  2. Violations of deleted resources/classes are assigned to the project
  • No labels