after upgrading SQ from 7.2 to 7.3 on Win10 gradle task (sonarqube) is NOT working.
With SQ 7.2 it all worked just fine (project has 100% groovy sources).
> Task :sonarqube FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':sonarqube'.
> org.sonar.plugins.groovy.codenarc.CodeNarcSensor has unsatisfied dependency 'class org.sonar.plugins.groovy.foundation.GroovyFileSystem' for constructor 'public org.sonar.plugins.groovy.codenarc.CodeNarcSensor(org.sonar.api.profiles.RulesProfile,org.sonar.plugins.groovy.foundation.GroovyFileSystem)' from org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@795f75c:261<[Immutable]:org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@2fb8e56c:235<[Immutable]:org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@3109f0f1:9<[Immutable]:org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@1016f71f:47<
In 7.3 we dropped a number of long-deprecated APIs, consequently making some plugins incompatible. Most of the relevant plugins had already been marked incompatible in the Marketplace, but we missed this one. I’ve just made the update in the Marketplace / Plugin Version Matrix. If you want to see this fixed, I urge you to enter a GitHub issue on the repository (and possibly submit a PR).
Unfortunately, this means that you’ve upgraded to a version which doesn’t support all of your projects, and there’s no downgrade except to revert to the database backup you made before upgrade.
Hi,
thans Ann for Your information. I’d like ask if is any chance that groovy will be supported in SQ 7.3 (or higner version) in the future. Or if the support is at the end. I have the same problem as kszymko.
It’s entirely possible that the Groovy analyzer lost compatibility at an earlier point in the SonarQube history and it just wasn’t noticed. To verify before I change things in the Marketplace: You’re using SonarQube 7.0 and version 2.4.13 of the Groovy analyzer and getting errors?
The Groovy plugin remains in the Marketplace, and will as long as it maintains compatibility with the most recent LTS. Therefore it still shows up in the Plugin Library page. But SonarSource hasn’t supported it for quite some time, which is one reason it’s listed in the “Other Languages” category.