-
Notifications
You must be signed in to change notification settings - Fork 10
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
A multitude of JRE/JDK related problems #8
Comments
JSweet only works with JDK because you need the Java compiler, and version 8 because you need the lambdas.... At some point the transpiler was raising a nice error when a JDK 8 was not found in the path. But obviously, this regressed -- it is hard to test such things :( |
OK but then again: which JDK shall I use with the jsweet plugin? JDK1.8.0_31 and JDK1.8.0._74 (latest version available) generate the displayed stacktrace... |
I don't have the answer to that question yet. I personally use 1.8.0_65. So the different stack traces probably just reflect an implementation difference... the problem being the stacktrace itself (maybe another bug). I will investigate ASAP. |
I must say that I am lost on this one. I use version 1.8.0_65, I have a server using 1.8.0_60 and Travis CI uses 1.8.0_31 (same as one you mention). All these three versions work fine. I am 99.9% sure that it is not a version problem, but something more subtle. Maybe you have previous errors that are not shown in your report? Questions: did you manage building with Maven? (like just building the quickstart project for instance). If yes, what was the JDK version? Do you manage to build with Maven the same JDK as the one you are launching Eclipse with? |
OK. I started over with my Windows laptop. Here are my findings. JSweet uses the I just tried to point to a JDK 1.6 and got that message. So, the point is that the first thing to do is really to revert your hack that made Eclipse point to a JDK 1.8. JSweet was never intended to work this way, and on all my Windows systems (I have 2 laptops under Windows 7 and 8.1) and all my Eclipse installations (Kepler, Luna, and Mars), JSweet worked without having to hack Eclipse. (Note that it should work anyway if you set the right Once it is reverted, check your So, make sure that you set your I hope this will work as expected. I am curious to see what you get. Additional info: I just filled an issue so that the plugin can work without having to rely on the |
I confirm that having the workaround of JAVA_HOME pointing to a JDK8 installation allows me to use jsweet from within Eclipse. Thanks! BTW: I cannot remove the JRE8 from the eclipse.ini file though. This I need because otherwise, a JRE7 is found, and the jsweet eclipse plugin is compiled with Java 8 sourcelevel compatibility... But that's a smaller issue. |
There are a multitude of JDK-related problems:
Here, the relevant stacktrace from the Eclipse error log:
Here, the relevant stacktrace from the Eclipse error log:
The text was updated successfully, but these errors were encountered: