|Re: Eclipse compatibility with Java updates [message #1784639 is a reply to message #1784628]
||Sat, 31 March 2018 14:16
| Stephan Herrmann
Registered: July 2009
Regarding the specific timing of your question: we have finalized Java 10 support for the 4.7.3a release (scheduled to go public on Apr. 11) just now. Until that release a few rough edges are not only to be expected, but Eclipse lives from the feedback of its users during development. In this regard you are more than welcome to report issues with unreleased features directly into bugzilla (well, looking for existing reports of the same issue is of course highly appreciated :) ).|
As for predicting future Java versions, you may recall that Java 10 was originally announced as "18.3", only later renamed to "10". Since we never knew how to detect compatibility of future versions, JDT has a tradition of waiting until a new version is (about to be) released, before we recognize it as compatible. It is a valid point - already being discussed - whether from now on recognizing Java versions should apply the announced scheme of future Java versions, rather then relying on a fixed set of known versions.
I'm not 100% sure what you mean by "letting the JVM make the decision". There is no way of asking a JVM "are you compatible with Java 9" or such. Moreover, JDT needs to be able to read .class files. If we are presented with a class file from a version that JDT does not understand, there can be no guarantee that the tooling will "just work". In some cases it can't.
As you mention Java 9 in particular, maybe we should even raise a much stronger warning when working on Java 8 projects using JDK 9, because chances are that the Java 8 program will *not* run out-of-the-box on JDK 9 ;-p
Powered by FUDForum
. Page generated in 0.01830 seconds