That is from April 2015… and to be clear would only be used if you are building SonarQube plugins. If you just want to run a SonarQube scan, you only need the sonar-maven-plugin referenced. Check the documentation on the SonarScanner for Maven.
To be honest, I’m not exactly sure in what context the error is being thrown (during compilation, durin g analysis…) so it would be great if you could provide some full logs related to the error.
And, SonarQube v9.4 has been EOL since SonarQube v9.5 coming out. We ask users to be using a supported version of SonarQube before trying to troubleshoot issues.
Thank you for your input.
We have planned our SQ upgrade to v9.9 LTS by next week. I’d be obliged if we can keep this ticket open until then.
I’ll check the settings & plugin configurations on the upgraded version & will update here.
Meanwhile, i’ll re-run the plan & fetch logs, will try to post it here in a text file for more clarification.
Edit: I found this in my pipeline logs:
— sonar-maven-plugin:18.104.22.1684:sonar (default-cli)
So I’m using the latest plugin