I started this topic once without getting far. Reason is that we do have
1 ruleset for all projects. Changing them would affect all projects on
sonar.
Goes into the same direction like having common coding guidelines,
formatter settings, ...
Don't get me wrong, I would very well appreciate that, but needs to be
discussed in a broader context.
Christian
On 20.09.2017 13:49, Karsten Thoms wrote:
I have started to raise Bugzilla requests to optimise the SonarQube
rules configuration. I believe that some rules are of no value for
certain file patterns and just distracting from real issues. With your
input we could make more use of the SonarQube reports and concentrate
on fixing issues detected by it. I posted already on cross-dev, but
without reaction so far.
[1] Bug#522282 - [sonar] Change rules for Message classes
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=522282>
[2] Bug#522285 - [sonar] Exclude generated EMF Package/Factory Impl
classes <https://bugs.eclipse.org/bugs/show_bug.cgi?id=522285>
[3] Bug#522482 - [sonar] Change rules for Test classes
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=522482>
~Karsten
_______________________________________________
platform-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-dev
