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 59 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 Sonar.

It leverages CodeNarc for coding rules violations, Gmetrics for cyclomatic complexity and Cobertura for code coverage.

Plugin

0.1

0.2

0.3

0.4

0.50.6

CodeNarc

0.9

0.9

0.13

0.15

0.16.10.17

GMetrics

0.2

0.2

0.3

0.3

0.40.5

cobertura-maven-plugin

(error)

2.4

2.5

2.5

2.5.12.5.1

Installation

  1. Install the Groovy plugin through the Update Center or download it into the SONAR_HOME/extensions/plugins directory
  2. Restart the Sonar server

Usage

Run a Sonar Analysis with the Sonar Runner (Recommended Way)

To launch a Sonar analysis of your Groovy project, use the Sonar Runner.

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

Run a Sonar 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 previously generated report from CodeNarc by setting the sonar.groovy.codenarc.reportPath property.

Metrics

See Metrics documentation page.

Known Limitations

The source directory must be added to the pom.xml, even if the project is built with Maven. This comes from the fact that Sonar does not call gmaven plugin.

Change Log

Loading

Release 0.6 (8 issues)

 

Loading

Release 0.5 (3 issues)

 

Loading

Release 0.4 (3 issues)

 

Loading

Release 0.3 (11 issues)

 

Loading

Release 0.2 (5 issues)

 

Loading

Release 0.1 (4 issues)

  • No labels