Thanks for your answer Michael.
We are creating a fresh local maven repository from scratch on every build, so it should only contain artifacts consumed or created by this build. This local repository is then used for sonar.java.libraries property.
As this is a quite large project (about 420k LoC) this local repository contains more than 2400 individual jar files. To be honest I don’t know if the scope of these libraries can be restricted further. Last but not least because the supported wildcard syntax is quite a limiting factor here.
I also made a quick test by running sonarScanner maven plugin with self discovering the libraries, but that did not make any difference in performance.
You indicated, that you are aware of issues related to creating the semantic model. Can you reveal more details here? Is there a timeline when a solution can be expected? Maybe we can stay at Sonar 7.9 until there is a fix in sight.