| Re: [platform-dev] SonarQube Configuration |
I asked Frederic. Exclusions can be specified either global or project-specific. We could try to define a quality profile for Platform, if we could agree on some rules. I would start with the ones defined by the bugs, if they are OK. Then projects would have to opt-in that they want to use that profile. We could start with platform.ui as a reference, maybe a second one (e.g. platform.debug) and then see if we get the desired effect.Am 20.09.2017 um 15:53 schrieb Christian Pontesegger <christian.pontesegger@xxxxxx>: ______________________________That was my status ~2 years ago. Possibly sonar admins will change that and add more profiles. Currently I see ony some [1]
Christian
[1] https://sonar.eclipse.org/
profiles
On 20.09.2017 15:20, Karsten Thoms wrote:
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
_________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
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
platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-dev