Hi @Dorian_Burihabwa , thank you very much for the quick response.
Some of our AzureDevOps Pipelines use the SonarSource-Tasks provided like this:
steps:
- task: SonarQubePrepare@7
...
- task: Maven@4
goals: verify
sonarQubeRunAnalysis: true
- task: SonarQubePublish@7
...
The sonarQubeRunAnalysis:true Parameter forces the maven call to be extended by this goal:
mvn ... verify .. org.sonarsource.scanner.maven:sonar-maven-plugin:RELEASE:sonar
which ends up in this warning
[WARNING] Using RELEASE instead of an explicit plugin version may introduce breaking analysis changes at an unwanted time. It is highly recommended to use an explicit version
Is this the same or different issue. Will this be hit by the relocation problem also?
Kind regards,
Dirk