Hi Paul,
it is no problem for me for now. It is not an urgent merge request. I
was only puzzled by the quality gate - like you too
bye Jochen
On 5/20/26 01:08, Paul King wrote:
I am still getting up to speed on Sonar. As a project we can define
our own gates and profiles.
The weird thing about the deprecation warning is that it is marked
Info level, nothing like blocker or high. I don't know why it then
ranks the submission as grade C.
I'll try to work it out, but I'm busy for the next few hours. I also
haven't worked out how to add other users to have the right
permissions to tweak the gates and profiles. I only obtained
permission myself a day or two ago. I'll try to work that out too. An
INFRA ticket might be the answer in the meantime if we can't
self-serve that.
Cheers, Paul.
On Wed, May 20, 2026 at 7:15 AM Jochen Theodorou <[email protected]> wrote:
Hi,
currently the quality gate for my merge request
github.com/apache/groovy/pull/2546 is failing because of
https://sonarcloud.io/project/issues?sinceLeakPeriod=true&issueStatuses=OPEN%2CCONFIRMED&pullRequest=2546&id=apache_groovy&open=AZ5BMcqnc-PA8pjUJITA&tab=code
That is me adding a deprecated flag to the class and I assume sonar
fails that because the class is 11 years or so old and now assumes it
had been deprecated since then? I am trying to understand the problem
here. Can somebody help me? Because the reasoning I showed surely does
not make a lot of sense
bye Jochen
