You are viewing an old version of this page. View the current version.
Compare with Current ·
View Page History
Plugins under development
Name |
Type |
Description |
|---|---|---|
Report |
A plugin for Sonar to post information on Twitter. |
|
Report |
Integration of Testability-explorer, a tool which analyzes Java bytecode and computes how difficult it will be to write unit tests for the code |
|
Report |
Integration of Hammurapi, a code review system that captures coding best practices |
|
Rules engine |
Jlint will check your Java code and find bugs, inconsistencies and synchronization problems by doing data flow analysis and building the lock graph. Jlint is extremely fast - even on large projects, it requires only one second to check all classes! It is easy to learn and requires no changes to the class files. Jlint has been used in an industrial environment and successfully uncovered faults with little effort! |
|
Language |
Analyze C and C++ languages |
|
Language |
Integration of JTest from Parasoft |
|
TimeMachine |
Re-creates history for a project automatically |
|
Language |
Consume the output from CodeNarc(violations) and GMetrics(metrics) and put it into Sonar. |
|
Report |
See SONARPLUGINS-132 |
|
Tests coverage |
JaCoCo is an alternative to Clover and Cobertura to measure coverage by unit tests. |
|
Report |
|
Wish list
You'd like to contribute to Sonar development but don't have a killer idea to start from. Here are several suggestions of possible plugins :
Name |
Type |
Description |
|---|---|---|
Macker |
Rules engine |
Use Macker to define and check architectural rules (SONARPLUGINS-35) |
Metrics list |
Report |
Reports on the complete list of metrics store in Sonar |
TestNG |
Unit tests |
TestNG is only supported in Maven projects (via Surefire), but not in other kinds of projects (when sonar.dynamicAnalysis=reuseReport). |
FOSSology |
Report |
License analysis by integrating http://fossology.org/ |
Labels
