-
Notifications
You must be signed in to change notification settings - Fork 125
Import Getting Start Content fails with Java 12 #393
Comments
Started STS with JDK 12.0.2. (Added
Which STS version did you use? |
Spring Tool Suite 4 |
I've also tried to reproduce and it works fine for me too. This error sounds like something that dates back from around Java 1.8 days when the logic around java version numbers changed. So maybe @vogella somehow is having some older versions of plugins installed. Though I have no idea where he'd be getting them from if he really is using STS 4.4.0 snapshot. How did you install STS Lars? Did you use the distribution build or install some things manually using a bunch of different update sites? I would also be interested in seeing the full stacktrace of that error as it may help pinpoint more precisely who is the 'culprit' for raising that error and will help focus the search for the suspected 'old plugin'. |
I downloaded from https://dist.springsource.com/snapshot/STS4/nightly-distributions.html spring-tool-suite-4-4.4.0.CI-B1961-e4.13.0-linux.gtk.x86_64.tar.gz at least the platform feature version looks fine for me Eclipse.org Eclipse Platform 4.13.0.v20190821-0600 org.eclipse.platform |
Full Java string: java --version |
I have only tried on e4.12... will try e4.13 |
Full stack trace: java.lang.reflect.InvocationTargetException |
Buildship issue? |
I see it now if I pick Gradle (Buildship 3.0)... your screenshot was misleading ;-) It has Maven selected... |
Sorry for the wrong screenshot
Alex Boyko <[email protected]> schrieb am Mo., 26. Aug. 2019, 19:01:
… I see it now if I pick Gradle (Buildship 3.0)... your screenshot was
misleading ;-) It has Maven selected...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#393>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABCFBWD6PA2IY4F4L6563LQGQD5VANCNFSM4IPOTKFA>
.
|
The error trace seems to point finger at gradle (or maybe buildship) as the culprit. If I had to guess the reason is the version of gradle:
Seems the trace says the version parse error is coming directly from some Gradle code. And my guess is that this is because the gradle version 4.6 which is used by the imported project is too old to be used with Java 12. So I don't think its a BuildShip issue but simply a normal limitation of the gradle version used by the imported project. |
So what is the essence of this? If you run your IDE on JDK 12, it throws an error if you select certain projects in the wizard and Gradle? That sounds quite unfortunate, to be honest. |
Trying to import the Getting Started Content results in the following error:
IllegalArgumentException: Could not determine java version from '12.0.1'.
java.lang.reflect.InvocationTargetException
The text was updated successfully, but these errors were encountered: