Hi Michel,
The bug seems to occur only when the sonar.rules.extensionsPath property is defined in the sonar.properties configuration file.
To contribute to the sonar documentation, you just have to create a Codehaus Confluence account and to be logged in.
The documentation is yours :-)
Freddy
On Thu, Jun 25, 2009 at 10:23 AM, Michel Pawlak
<michel.pawlak@...> wrote:
Confirmed. However, it's a CS description file, not a PMD one. I just
reported issue 941, I'm wondering if it's not related to this behavior (i.e.
the CS description file is read when loading PMD extensions, which may
explain why CS rules are registered as PMD and findbugs ones)
The documentation page should be documented :
If I had access to it I would do it. Is there any possibility to contribute
directly to the documentation ?
Michel
Freddy Mallet wrote:
>
> Thanks for this notification Michel. Could you confirm a description field
> was missing in your CS rules description file ?
> Freddy
>
> ----------------------------------------
> Freddy Mallet
>
www.SonarSource.com
>
Sonar.codehaus.org
>
http://twitter.com/FreddyMallet
> ----------------------------------------
>
>
--
View this message in context: http://www.nabble.com/Sonar-1.8-%22can-not-synchronize-rules-extensions-of-plugin-%3A-pmd%22-tp24180418p24199033.html
Sent from the Sonar user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
