-
Notifications
You must be signed in to change notification settings - Fork 317
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
java.lang.NoSuchMethodError: 'void com.google.common.base.Throwables.throwIfUnchecked(java.lang.Throwable)' #1772
Comments
xtext has no guice 4 support. |
I changed guice version to 3.0:
It seems that the problem was with
Seems that switching to guice 3.0 doesn't help, I get the same exception. Also I've found the following errors in the build log (these errors was with guice 4 too):
|
the asm version looks bad. |
hmm i cloned and the build seems to work fine
also the gradle version (xtext tests with 5.6.3) and the xtext-gradle-plugin (current version is 2.0.8) |
do you have something to clone? |
You can change something in file https://github.com/eclipse/sprotty-server/blob/master/org.eclipse.sprotty/src/test/java/org/eclipse/sprotty/DefaultDiagramServerTest.xtend and try to build the project. This modification will force Java-code regeneration, causing the exception |
am still getting test fails only and not compile errors (both linux and windows) |
Thanks a lot! PATH variable pointed to JDK 1.8. But JAVA_HOME was set to JDK 13. Changed it to 1.8, and the project is build fine. Only tests are failed. I don't understand the exact cause of the error. But it seems that it is solved now. Thanks! |
you use a old gradle version and a plugin version but with gradle 5.6.3 + plugin version 2.0.8 it should work with 13 too |
Hi
I'm trying to build sprotty-server
I cloned it's repository and executed
gradlew build
on Windows 10 and JDK 1.8. One of the tests is failed, so I'm trying to change this test and rebuild the project.The problem is that the test is written on Xtend and I get the following exception:
The project depends on guava 27.1-jre and everithing seems to be fine:
Maybe the problem is related to #1391 ?
Could you please help to fix this bug?
The text was updated successfully, but these errors were encountered: