While testing the upgrade for SonarQube Server 2025.1 I found that there is a new rule java:S6809 that finds wrong usage of Spring proxied methods (e.g. @Async or @Transactional) when calling them via “this” on the same instance.
But in previous SonarQube versions the rule java:S2229 already existed that checked for the wrong usage of @Transactional methods.
Now when this problem occurs in 2025.1 we get the same finding twice. Once for every rule.
Is there a specific reason java:S2229 is still active and not deprecated yet? If not I will simply deactivate it in favor of java:S6809 that has support for multiple annotations anyways.
Kind Regards,
Daniel