SonarQube 7.6 breaks @ScannerSide annotation

SonarQube: 7.6
Sonar Scanner: 3.6.0.1398

Error discussed here:

GitLab plugin stopped working.
@ScannerSide was deprecated in 7.6, package was moved:
org.sonar.api.batch.ScannerSide -> org.sonar.api.scanner.ScannerSide

GitLab plugin still used the old one for backwards-compatibility, but this does not work. Updating to the new one worked.

I imagine this could affect many plugins.

Edit: minor errors, sorry for the brevity of this report, it’s been a long day :slight_smile:

1 Like

Hi Lukas,

I replied on GitHub, but just for people reading this thread, the change that is affecting you is:
https://jira.sonarsource.com/browse/SONAR-11486

Starting from 7.6, PostJob is proper project level component (instead of a module level one, but only executed on root module), and consequently can’t see module level components.

Solution by @Julien_HENRY works.

The issue is not with @ScannerSide as such, but rather the PostJob which the new @ScannerSide just happened to fix.

Thanks for the support!

Hello @Julien_HENRY and @lukaspj ,

I update my plugin to 4.0.0 but I have always the issue com.talanlabs.sonar.plugins.gitlab.CommitPublishPostJob has unsatisfied dependency
at the end of my analyse.

Do you how I can fix this ?

Thanks

Hi @aehanno,

I don’t think the gitlab plug-in is maintained anymore.
I think the integration is built into SonarQube in newer versions.

If you really need to use the plugin, I think you have to build it yourself or use my snapshot.

See this issue: https://github.com/gabrie-allaigre/sonar-gitlab-plugin/pull/214