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

Live example

Icon

If you want to see a live example of the capabilities of the Groovy plugin, you can have a look at the analysis of the CodeNarc project on Nemo.

Description / Features

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

cobertura-maven-plugin

(error)

2.4

2.5

2.5

2.5.12.5.12.5.1

Installation

  1. Install the plugin through the Update Center or download it into the SONARQUBE_HOME/extensions/plugins directory
  2. Restart the SonarQube server

Usage

Run an Analysis with the SonarQube Runner (Recommended method)

To run an analysis of your Groovy project, use the SonarQube Runner.

A sample project is available on github that can be browsed or downloaded: /projects/languages/groovy/groovy-sonar-runner.

Run an Analysis with the other Analyzers

Maven and Ant can also be used to launch analysis on Groovy projects.

A Maven sample project is available on github that can be browsed or downloaded/projects/languages/groovy/groovy-maven.

Advanced Usage

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

Metrics

See Metrics documentation page.

Known Limitations

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.

 

  • No labels