Update on tackling Sonar Findings

I would like to give a short update on our Sonar Findings.

Starting from 16k issues that Sonar raised with default settings on the inherited code base, we have been continously working on addressing them. The ultimate goal is address each of them and continue to tackle any new finding. We are aware that this goal is very ambituous and almost impossible to reach, but we will continously work on code quality.

In the first months we could solve a large amount with the help of OpenRewrite. But a vast amount of them has been tackled by manual work. This work was often schematic and issues could be solved by refactorings.

The potential of resolving issues easily decreases now steadily. More and more issues can’t be solved (yet), because e.g.

  • It would require refactorings that break API (removal/change of method parameters, change class hierarchy, API visibility changes)
  • Lack of knowledge about intention in inherited code
  • Deprecations that can’t be removed (because of one of both before mentioned points)

And we come more and more to the point that many Sonar issues have to be carefully investigated case by case.

To give you an imagination on the achievements we gained until today:

Release Date # Sonar Issues Change to before
Beta-1 2024-11-02 16.612
Beta-2 2024-02-03 14.237 -12 %
Beta-3 2025-01-31 8.274 -42 %
Beta-4 2025-05-07 4.053 -51 %
Beta-5 (In progress) 2025-06-06 (snapshot) 3.156 - 22 %

I would like to call YOU to action to tackle findings and provide Pull Requests. There are the following “umbrella” issues that you could refer to:

It is still mass work to do, your work would really help us.

2 Likes