Error caused by: com.talanlabs.sonar.plugins.gitlab.CommitPublishPostJob has unsatisfied dependency #213
Comments
|
No idea, but I have the same issue. I get it running from Gradle, with just a URL and login defined. So it should not even try to report anything on GitLab. The SonarQube installation is fresh, with just this and the SAML plugin installed. Environment:
|
|
#metoo with SonarQube 7.6 and plugin 4.0.0 |
|
Can confirm. Full stack-trace: |
|
I have tried compiling the GitLab plugin with both OpenJDK and OracleJDK 8, both give the same error. What Java version are you guys using to run the Sonar Scanner? |
|
On a sidenote, the FindBugs plugin has the same issue with the latest version(s), so i think this is an issue caused by SQ 7.6. |
|
Found a lead. |
|
Can confirm, using the new @ScannerSide annotation works. |
|
Created a bug-report on SonarSource community: |
|
@lukaspj nice find! Any chance you can detail your work fix? |
|
Sure thing, And update Sonar version in pom.xml to 7.6 Compile and upload and done 👍 |
|
Worth noting, this isn't a correct fix as such. Because it breaks backwards compatibility with previous versions of SonarQube. It should be fixed by SonarQube itself. |
|
Hi @lukaspj In SonarQube 7.6 we have started getting rid of our historically high coupling with Maven modules. The change that is affecting you is https://jira.sonarsource.com/browse/SONAR-11486 Basically, prior to 7.6, the PostJob extension point was a module level component, but only executed on the root module, at the end of the analysis. Since we are progressively trying to get rid of modules, we have changed the PostJob extension point to a project level component. In your situation, the problem is that your post job ( If you want to fix your plugin to support both SQ 7.6 and earlier versions, I think the easiest way is to make all your components project level, but not using the new Let me know if you need more informations. |
|
Same problem 😭
|
|
Same error here |
|
@ripper2hl, @n20 have you tried the snapshot mentioned here? |
|
yes i used this package |
|
can confirm with the official image of sonarqube 7.6 and sonar-gitlab-plugin 4.0.0 |
|
Same error with SonarQube 7.7 |
|
same error with SonarQube 7.7 and sonar-gitlab-plugin 4.0.0 |
|
Using the sonar-gitlab-plugin-4.1.0-SNAPSHOT.jar fixed it for me, now I just need to figure out how to get my reports into gitlab now that analysis mode report is no longer 😕 |
|
Had the same issue, can confirm, that sonar-gitlab-plugin-4.1.0-SNAPSHOT.jar fixed it. Thank you @vitosans |
|
In my case, I have this error during Jenkins integration with Sonar |
Ty @vitosans |
|
Trying to understand... A recent change to SonarQube (the server) has broken scanner plugins, and this has to be fixed in "sonar itself" meaning... the server? No, the scanner! (maybe?) Using SonarQube server 7.6, sonar-maven-plugin 3.6.1.1688, and jacoco-maven-plugin 0.8.4, I too get e.g.: (Not using a gitlab plugin.) |
|
Are we talking about a Maven build plugin used when we do the scan on the code, or the server-side plugin? |
|
For those as clueless as I was about this problem, we are talking about a plugin installed in the SonarQube server. To uninstall, go to <your_sonar_site>/admin/marketplace?filter=installed and look for "Gitlab." Click the Uninstall button for any Gitlab-related plugins. After a restart, you should be able to scan without getting the same error for the same reason (worked for me). |
|
Same error with SonarQube 7.9.2 and sonar-gitlab-plugin 4.0.0 |
|
Any new about this bug?
How can I pass through it? because the only side effect that I saw, it's about the status of my pipeline on gitlab but not on my sonar server, because the project has been scanned. Regards |
|
Why don't you guys just use SQ 8+? As far as i understand, it has all that functionality now built in. |
|
Unfortunatelly, that integration is only for commercial edition and NOT for the community one, so I hope someone has solved the bug or I have just to wait for the next version of the maven plugin. |
|
Remove any related plugin to gitlab at sonarqube and the issue will be solved |
|
Could the 4.1.0 be released so the fix for this bug would be in a relea? |
|
I'm still having the same error using the sonar scanner maven plugin Any suggestion? Stefano |
it is only in commercial version, but my boss seem does not want to pay for it with sonar-gitlab-plugin 4.1.0 i got exception like: my sornarqube version is :8.3 community edition @gabrie-allaigre ? is this plugin support sonarqube 8.3 ? need help, thanks alot |
|
SonarQube 7.9.2
|
I have the same problem, I wish next version of maven plugin can solve it, or someonelse has a workaround? |
|
I have the same problem about: [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.7.0.1746:sonar (default-cli) on project cp-parking: com.talanlabs.sonar.plugins.gitlab.CommitPublishPostJob has unsatisfied dependency 'class com.talanlabs.sonar.plugins.gitlab.ReporterBuilder' for constructor 'public com.talanlabs.sonar.plugins.gitlab.CommitPublishPostJob(com.talanlabs.sonar.plugins.gitlab.GitLabPluginConfiguration,com.talanlabs.sonar.plugins.gitlab.SonarFacade,com.talanlabs.sonar.plugins.gitlab.CommitFacade,com.talanlabs.sonar.plugins.gitlab.ReporterBuilder)' from org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@531a1bef:428<[Immutable]:org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@6cd76944:55<| -> [Help 1] I hope anyone can give a greate solution 。Thank you very much！ |
|
Good evening, I hope with the latest version the problem has been solved but unfortunately, I observed the same error: [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.8.0.2131:sonar (default-cli) on project ****: com.talanlabs.sonar.plugins.gitlab.CommitPublishPostJob has unsatisfied dependency 'class com.talanlabs.sonar.plugins.gitlab.ReporterBuilder' for constructor 'public com.talanlabs.sonar.plugins.gitlab.CommitPublishPostJob(com.talanlabs.sonar.plugins.gitlab.GitLabPluginConfiguration,com.talanlabs.sonar.plugins.gitlab.SonarFacade,com.talanlabs.sonar.plugins.gitlab.CommitFacade,com.talanlabs.sonar.plugins.gitlab.ReporterBuilder)' from org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@15295502:274<[Immutable]:org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@47ba1758:46<| -> [Help 1] |
|
New plugin version from this fork works for us: https://github.com/javamachr/sonar-gitlab-plugin |
and others
Hi,
Just started using SonarQube and am trying to integrate with our GitLab, however having issues with what seems to be the GitLab integration.
I am also using GitLab Auth, and have installed the 4.1.0-SNAPSHOT.
Environment:
Test
.gitlab-ci.ymljob:Any ideas?
Thanks
The text was updated successfully, but these errors were encountered: