JDK 13 support for Gradle

Just updated to JDK13. None of the java imports and primitives are recognized. Any known issues with JKD13? Cleaned language server workspace with the same result.

Environment

• Operating System: Windows 10 x64
• JDK version: 13
• Visual Studio Code version: 1.39.0 (Insiders)
• Java extension version: 0.49.0

Steps To Reproduce

1. Create JDK13 project in VSCode
2. Open Java file

Entry in .classpath file (jdk 13):

<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-13/"/>

Multiple exceptions in output from Extension:

Can’t convert ‘13’ to enum type ‘JavaVersion’

Caused by: java.lang.IllegalArgumentException: Cannot convert string value ‘VERSION_13’ to an enum value of type ‘org.gradle.api.JavaVersion’ (valid case insensitive values: VERSION_1_1, VERSION_1_2, VERSION_1_3, VERSION_1_4, VERSION_1_5, VERSION_1_6, VERSION_1_7, VERSION_1_8, VERSION_1_9, VERSION_1_10, VERSION_11, VERSION_12, VERSION_HIGHER)

[fbricon]

I’m testing 3.1.3 in jdt.ls builds. Hopefully we should be able to provide a CI build tomorrow

[astrelsky]

So I managed to resolve this locally from the advice here https://github.com/eclipse/eclipse.jdt.ls/issues/1196#issuecomment-544814496

I launched eclipse and waited the usual 20 minutes for it to start. Waited another 20 minutes for it to transition to the welcome screen. Added the snapshot to grab that update and then exited eclipse. I then searched my user directory for ‘buildship’ and located the following two jar files:

C:\Users\{user}\.p2\pool\plugins\org.eclipse.buildship.core_3.1.3.v20191025-2152-s.jar
C:\Users\{user}\.p2\pool\plugins\org.gradle.toolingapi_6.0.0.v20191025-2152-s.jar

I then copied those two files into C:\Users\{user}\.vscode-insiders\extensions\redhat.java-0.53.0\server\plugins I then opened C:\Users\astre\.vscode-insiders\extensions\redhat.java-0.53.0\server\config_win\config.ini and replaced@4,reference\:file\:org.eclipse.buildship.core_3.1.2.v20190903-1732.jar with @4,reference\:file\:org.eclipse.buildship.core_3.1.3.v20191025-2152-s.jar and @4,reference\:file\:org.gradle.toolingapi_5.6.1.v20190903-1732.jar with @4,reference\:file\:org.gradle.toolingapi_6.0.0.v20191025-2152-s.jar

After that I re-opened vscode, cleaned the language server workspace and after a couple seconds I was able to work again (debug, build, test, etc.). Is this method recommended? No. I just hope it pushes things in the right direction.