Plugin incompatible with 10.1.0 SonarQube bug #782
Comments
|
I have the same problem on a windows server running sonarqube as a service. The service is starting and after a while stops with the following error on the web.log file of sonarqube. If I comment out the two properties sonar.web.javaAdditionalOpts and sonar.ce.javaAdditionalOpts in the configuration file then the application starts correctly. 2023.06.28 21:04:39 WARN web[][o.s.c.a.AnnotationConfigApplicationContext] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'jdk.internal.loader.ClassLoaders$[email protected]': Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@6f94fa3e-com.github.mc1arke.sonarqube.plugin.server.pullrequest.ws.pullrequest.PullRequestWs': Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@6f94fa3e-com.github.mc1arke.sonarqube.plugin.server.pullrequest.ws.pullrequest.action.ListAction': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.github.mc1arke.sonarqube.plugin.server.pullrequest.ws.pullrequest.action.ListAction]: Constructor threw exception; nested exception is java.lang.IncompatibleClassChangeError: Inconsistent constant pool data in classfile for class org/sonar/server/ws/WsUtils. Method 'void writeProtobuf(com.google.protobuf.Message, org.sonar.api.server.ws.Request, org.sonar.api.server.ws.Response)' at index 432 is CONSTANT_MethodRef and should be CONSTANT_InterfaceMethodRef |
|
I can confirm this. |
|
Hello could it be possible that SonarQube version should be updated in file build.gradle to match proper version 10.1.0.73491 ? Sorry i don't have a 10.1 instance at hand to test, maybe you could build locally and see if it works |
based on the branch: feature/sonarqube-10_0-support
1. upgrade sonarqubeVersion to '10.0.0.68432'
2. fixed dbClient.componentDao().insert(DbSession session, ComponentDto item, boolean isMainBranch)
3. fixed UT code
I have make a pull request for that: Tested in the 10.1.0 SonarQube instance |
based on the branch: feature/sonarqube-10_0-support
1. upgrade sonarqubeVersion to '10.0.0.68432'
2. fixed dbClient.componentDao().insert(DbSession session, ComponentDto item, boolean isMainBranch)
3. fixed UT code
based on the branch: feature/sonarqube-10_0-support
1. upgrade sonarqubeVersion to '10.0.0.68432'
2. fixed dbClient.componentDao().insert(DbSession session, ComponentDto item, boolean isMainBranch)
3. fixed UT code
based on the branch: feature/sonarqube-10_0-support
1. upgrade sonarqubeVersion to '10.0.0.68432'
2. fixed dbClient.componentDao().insert(DbSession session, ComponentDto item, boolean isMainBranch)
3. fixed UT code
based on the branch: feature/sonarqube-10_0-support
1. upgrade sonarqubeVersion to '10.0.0.68432'
2. fixed dbClient.componentDao().insert(DbSession session, ComponentDto item, boolean isMainBranch)
3. fixed UT code
|
I had exactly the same problem using helm chart (V8), with a sonar 10 instance and sonarqube-community-branch-plugin-1.14.0. I was using the jvmOpts and jvmCeOpts properties, which according to the helm doc (https://github.com/SonarSource/helm-chart-sonarqube/blob/master/charts/sonarqube/values.yaml) were obsolete. So instead of I used and it works |
|
@bluebu Thank you for the fix, I tested it and it worked well. |
|
It does not work for me :(
|
|
@bluebu Thanks you for the fix. It's working for me! |
|
@Adjunior Is it possible to have this jar file publicly available from git please? |
|
@Adjunior, one can fetch the artifact here. https://github.com/bluebu/sonarqube-community-branch-plugin/actions/runs/5621946627 Download the snapshot.zip |
Updates to the Sonarqube APIs for version 10.1
Updates to the Sonarqube APIs for version 10.1
Sonarqube 10.1 includes classes compiled with a Java 17 target, so the plugin fails to compile in the container build that uses Java 11. The build container is therefore being bumped to Java 17, and the environment file configured to pin to Sonarqube 10.1 to allow repeated builds.
Sonarqube 10.1 includes classes compiled with a Java 17 target, so the plugin fails to compile in the container build that uses Java 11. The build container is therefore being bumped to Java 17, and the environment file configured to pin to Sonarqube 10.1 to allow repeated builds.
|
Sonarqube 10.1 support released in 1.16.0 |
Describe the bug
UI does not show up on upgrade to SonarQube 10.1.0
To Reproduce
Perform an upgrade to 10.1.0
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Software Versions
Additional context
Here is the error message:
The text was updated successfully, but these errors were encountered: