Sonar 1.11 and sonar.reuseExistingRulesConfiguration parameter

[Frederic Camblor]

Hi folks,

I just looked at the 1.11 release note and I wonder what is the real behaviour behind the all new sonar.reuseExistingRulesConfiguration maven parameter.

If I well understandd this parameter, it allows us to not duplicate checkstyle (and pmd and so on...) XML configuration among :

- the sonar quality profile

- the maven checkstyle plugin

=> the only one used will be the maven one

Nevertheless, what I don't understand is "how sonar know how to map 'home made checkstyle rules' into rules compliance categories ?" (the *-extension.xml)

I am a newbie with the sonar maven plugin, so maybe I misunderstand something in the workflow ... but it isn't clear in my mind :-)

Cheers,

Frédéric

[Freddy Mallet]

Your understanding is perfectly correct Frederic.

You just need the following piece of information :

Any violations on a rule not known by Sonar is ignored. You first need to declare this home made rules on the Sonar rules repository.

cheers,
Freddy

On Wed, Oct 14, 2009 at 9:05 AM, Frederic Camblor <fcamblor@...> wrote:

Hi folks,

I just looked at the 1.11 release note and I wonder what is the real behaviour behind the all new sonar.reuseExistingRulesConfiguration maven parameter.

If I well understandd this parameter, it allows us to not duplicate checkstyle (and pmd and so on...) XML configuration among :

- the sonar quality profile

- the maven checkstyle plugin

=> the only one used will be the maven one

Nevertheless, what I don't understand is "how sonar know how to map 'home made checkstyle rules' into rules compliance categories ?" (the *-extension.xml)

I am a newbie with the sonar maven plugin, so maybe I misunderstand something in the workflow ... but it isn't clear in my mind :-)

Cheers,

Frédéric

[Frederic Camblor]

Hi Freddy,

And thanks for the answers !

I don't know what the "sonar rules repository" is : is this what is described here ?

Cheers,

Frédéric

On Wed, Oct 14, 2009 at 9:37 PM, Freddy Mallet <freddy.mallet@...> wrote:

Your understanding is perfectly correct Frederic.

You just need the following piece of information :

Any violations on a rule not known by Sonar is ignored. You first need to declare this home made rules on the Sonar rules repository.

cheers,
Freddy

On Wed, Oct 14, 2009 at 9:05 AM, Frederic Camblor <fcamblor@...> wrote:

Hi folks,

I just looked at the 1.11 release note and I wonder what is the real behaviour behind the all new sonar.reuseExistingRulesConfiguration maven parameter.

If I well understandd this parameter, it allows us to not duplicate checkstyle (and pmd and so on...) XML configuration among :

- the sonar quality profile

- the maven checkstyle plugin

=> the only one used will be the maven one

Nevertheless, what I don't understand is "how sonar know how to map 'home made checkstyle rules' into rules compliance categories ?" (the *-extension.xml)

I am a newbie with the sonar maven plugin, so maybe I misunderstand something in the workflow ... but it isn't clear in my mind :-)

Cheers,

Frédéric

[Freddy Mallet]

Hi Frederic,

On Wed, Oct 14, 2009 at 10:57 PM, Frederic Camblor <fcamblor@...> wrote:

Hi Freddy,

And thanks for the answers !

I don't know what the "sonar rules repository" is : is this what is described here ?

It is !
The Sonar rules repository contains :
- all the native rules from checkstyle, pmd and findbugs
- all the rules associated to optional plugins like Taglist plugin
- all your own Checkstyle and PMD rules defined with the Sonar extension mechanism

cheers,
Freddy

On Wed, Oct 14, 2009 at 9:37 PM, Freddy Mallet <freddy.mallet@...> wrote:

Your understanding is perfectly correct Frederic.

You just need the following piece of information :

Any violations on a rule not known by Sonar is ignored. You first need to declare this home made rules on the Sonar rules repository.

cheers,
Freddy

On Wed, Oct 14, 2009 at 9:05 AM, Frederic Camblor <fcamblor@...> wrote:

Hi folks,

I just looked at the 1.11 release note and I wonder what is the real behaviour behind the all new sonar.reuseExistingRulesConfiguration maven parameter.

If I well understandd this parameter, it allows us to not duplicate checkstyle (and pmd and so on...) XML configuration among :

- the sonar quality profile

- the maven checkstyle plugin

=> the only one used will be the maven one

Nevertheless, what I don't understand is "how sonar know how to map 'home made checkstyle rules' into rules compliance categories ?" (the *-extension.xml)

I am a newbie with the sonar maven plugin, so maybe I misunderstand something in the workflow ... but it isn't clear in my mind :-)

Cheers,

Frédéric