That’s what I fear. Getting a common agreement is complicated. But is it really 
for *all* projects? In [1] Frederic configured the exclusion for Message 
classes on platform.ui only. So this seems possible to decide in on a project 
level to configure rules.

As you can see in [2] „Static Variable Names“ are not recorded for 
*Messages.java classes. In [3] the issue still exists. So it could be defined 
per project. And you could decide at least for platform projects to do so.

[1] Bug#522282 - [sonar] Change rules for Message classes
[2] platform.ui Query: 
https://sonar.eclipse.org/drilldown/issues/33359?&rule=checkstyle%3Acom.puppycrawl.tools.checkstyle.checks.naming.StaticVariableNameCheck&rule_sev=MAJOR&severity=MAJOR
 
<https://sonar.eclipse.org/drilldown/issues/33359?&rule=checkstyle:com.puppycrawl.tools.checkstyle.checks.naming.StaticVariableNameCheck&rule_sev=MAJOR&severity=MAJOR>
[3] platform.debug Query: 
https://sonar.eclipse.org/drilldown/issues/33429?&rule=checkstyle:com.puppycrawl.tools.checkstyle.checks.naming.StaticVariableNameCheck&rule_sev=MAJOR&severity=MAJOR
 
<https://sonar.eclipse.org/drilldown/issues/33429?&rule=checkstyle:com.puppycrawl.tools.checkstyle.checks.naming.StaticVariableNameCheck&rule_sev=MAJOR&severity=MAJOR>


> Am 20.09.2017 um 14:50 schrieb Christian Pontesegger 
> <[email protected]>:
> 
> 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] <mailto:[email protected]>
>> To change your delivery options, retrieve your password, or unsubscribe from 
>> this list, visit
>> https://dev.eclipse.org/mailman/listinfo/platform-dev 
>> <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

_______________________________________________
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

Reply via email to