Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 423651

Summary:	Treat unrecognized future JDKs as source code compatible with the latest known JDK version
Product:	[Eclipse Project] JDT	Reporter:	Timo Kinnunen <timo.kinnunen>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	4.3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 8
Whiteboard:	stalebug

Description Timo Kinnunen

2013-12-09 20:36:35 EST

This bug is the JDT Core portion of bug 423648 in JDT UI, which it may block. Please see it for more details.

Patches in Gerrit, for Core: https://git.eclipse.org/r/19553 for UI: https://git.eclipse.org/r/19552 

To improve user experience when people try a new version of Eclipse with Java 8 Early Access JDKs, an unknown JDK version should be assumed capable of working with the latest known JDK version in terms of source code compatibility. This is especially important when existing projects using workspace default JRE are imported to a new workspace managed by an Eclipse installation running on Java 8 EA VM. 

Currently projects that compiled without problems under a previous Eclipse-Java combination encounter build errors that are not solved by simply adding a Java 7 JRE to the installation. The 'trick' needed to solve the situation is not obvious: after adding the JRE, one needs to open Preferences->Java->Compiler page and click OK even if the page already claims that compliance level is set to 7.

The fix is simply to treat unknown JDK version strings as meaning compiler compliance 7.

Comment 1 Eclipse Genie

2018-11-27 15:21:13 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.