after all, I’m wondering how this error came about, because the plugin works otherwise.
There are only problems when starting an analysis, i.e. with Maven - didn’t try other scanners.
Does this possibly have something to do with it and maybe it’s fixed with Sonarqube 10.4 !?