As of today, Java 12 has reached general availability. However, it has been tested, and especially for building projects is known to not work for wpilib projects. If you used the installer, and are using the jdk and vscode from there, you are fine, and should be able to update your personal instance of java if you wish. However if you did not use the installer, or are using an alternate IDE, it’s recommended to not update, as Java 12 will not work correctly. We can’t add java 12 support to the build system until after the season, so you will need to keep 11 in order to build robot code.
9 Likes
What is the actual failure? Is there an issue filed that we can use to track the problems and progress fixing it?
Thank you for testing and discovering this.
Gradle 5.0 doesn’t officially support Java 12, and occasionally has some issues with class generation in groovy when running on Java 12. The fix is to update gradle, but we can’t update without breaking GradleRIO working in 5.0. It either works in 5.0, or works in 5.3. And we don’t want to force a midseason update to 5.3, so we will not be fixing this issue. There is an issue involving that update in GradleRIO, but it is won’t fix for 2019.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.