Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup
{iframe:src=http://update.sonarsource.org/plugins/groovy-confluence.html|width=700|height=220450|frameborder=0}
Your browser does not support iframes.
{iframe}

...

The plugin enables analysis of Groovy projects within SonarQube.

It leverages CodeNarc to raise issues against coding rules, Gmetrics for cyclomatic complexity and Cobertura for code coverage.

Plugin

0.1

0.2

0.3

0.4

0.50.61.0

CodeNarc

0.9

0.9

0.13

0.15

0.16.10.170.20

GMetrics

0.2

0.2

0.3

0.3

0.40.50.6

...

  1. Prior to the SonarQube analysis, execute your unit tests and generate the Cobertura XML report.
  2. Import this report while running the SonarQube analysis by setting the sonar.groovy.cobertura.reportPath property to the path to the Cobertura XML report. The path may be absolute or relative to the project base directory.

A sample project can be browsed or downloaded: TODObe browsed or downloaded/projects/languages/groovy/groovy-sonar-runner-cobertura.

CodeNarc

It is possible to reuse a previously generated report from CodeNarc by setting the sonar.groovy.codenarc.reportPath property.

...

See Metrics documentation page.

Known Limitations

  • The following piece of code won't be properly parsed because command expression is not currently supported.

    Code Block
    languagegroovy
    a = Arrays.asList 1,2,3,4,5
  • If you're analyzing with Maven, the Groovy source directory must be added to the pom.xml explicitly, because SonarQube does not call the gmaven plugin.

Release Notes

Version 1.0

It is no longer possible to:

  • let Let SonarQube drive the execution of unit tests.
  • import Import unit test execution reports let (feel free to vote for 
    JIRA
    serverjira.codehaus.org
    keySONARPLUGINS-3540
     to reintroduce this feature).
  • Let SonarQube drive the execution of Cobertura; it is now only possible to import previously generated Cobertura report.