-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use SonarQube tool with scala 2.12.8 #11352
Comments
this is @lrytz's area of expertise / cross to bear |
Hi Martin Could you double-check which exact jar/classfile is causing the issue? In 2.12.7 we started adding the Can you get the tool to tell you which method is the one causing the problem? |
@lrytz thanks a lot for the response and very sorry for the belated reply. The only exceptions I'm seeing in the logs are:
The only change that was introduced with the commit when these exceptions first started happening is updating:
The only suspicious thing I could find there is updating |
It looks like Kafka 2.1.0 itself was compiled with Scala 2.12.7 (and thus depends on scala-library 2.12.7) -- could you check the classpath to ensure only the 2.12.8 Scala library is on there? (2.12.8 and 2.12.7 are binary compatible, but the most recent version should not have the issue with bridges, as Lukas said) PS: and indeed, Kafka 2.0.0 was using Scala 2.12.6, so that would align well with Lukas's expectation. |
Hello,
we are using SonarQube (https://www.sonarqube.org/) to detect different kinds of issues with our code (our stack is Java 8 + Akka, but we are using some scala constructs in our code every now and then). After updating one of the libraries we are using to a new version SonarQube started outputting multiple errors like the one below:
Basically the error is always
java.lang.IllegalStateException: bridge method not marked as synthetic
and the scala class that is mentioned varies.I noticed that the new version of the library introduces a dependency to
scala 2.12.8
instead ofscala 2.12.7
(which is the scala version required by the old version of the library) and one of the changes mentioned in the release notes ofscala 2.12.8
is:So I believe that's what causes the SonarQube errors. Can someone please look into this?
Thanks,
Martin
The text was updated successfully, but these errors were encountered: