It seems v2.16.0.226 was unpublished from the Maven repo and is causing our scans to fail when looking for this package.
Is there a reason it was unpublished?
It seems v2.16.0.226 was unpublished from the Maven repo and is causing our scans to fail when looking for this package.
Is there a reason it was unpublished?
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.8.0.2131:sonar (default-cli) on project ****: Execution default-cli of goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.8.0.2131:sonar failed: Plugin org.sonarsource.scanner.maven:sonar-maven-plugin:RELEASE or one of its dependencies could not be resolved: Failure to find org.sonarsource.scanner.api:sonar-scanner-api:jar:2.16.0.226 in (masked) was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
same problem.
I have to fix version to avoid this error.
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.sonarsource.scanner.maven</groupId>
<artifactId>sonar-maven-plugin</artifactId>
<version>3.7.0.1746</version>
</plugin>
</plugins>
</pluginManagement>
Hi @JoeRistine
thanks for reporting the issue. We are working on it. The artifacts were not unpublished. Due to a pickup in the release pipeline they were not published at all.
Currently the MavenCentral Gateway seems to be very unstable.
To workaround this situation, the best option is to not depend on the LATEST
version and use 2.15.0.2182
instead.
If you are using the maven scanner please stay on version 3.7.0.1746
like @hankchan101 mentioned.
I will let you know, when all artifacts are available on MavenCentral.
Good news!
sonar-scanner-api:2.16.0.226 is available on Maven Central now.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.