Bug 498279 - No Compatible JREs after updating java to 1.8.0_102
Summary: No Compatible JREs after updating java to 1.8.0_102
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.5.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2016-07-21 09:17 EDT by Yannis Kargakis CLA
Modified: 2019-12-20 10:20 EST (History)
4 users (show)

See Also:

Attachments
screenshot (189.24 KB, image/jpeg)
2016-07-21 09:17 EDT, Yannis Kargakis CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yannis Kargakis CLA 2016-07-21 09:17:42 EDT 
Created attachment 263239 [details]
screenshot

Hello,
After updating java to 1.8.0_102 eclipse does not show compatible execution environments to JavaSE-1.8 (see attached screenshot).

There is no a solution for me to change JRE library from Java Build Path on the properties of the project, since after a maven update the jre library still to be unbounded.

Any help?
Thanks,
Comment 1 Yannis Kargakis CLA 2016-07-21 09:23:09 EDT 
Releted envirometns (JAVA_HOME,Path etc) have been set it properly
Comment 2 Andrey Loskutov CLA 2016-07-22 03:27:22 EDT 
Please try to check if you see the same behavior with 4.6.0.
Comment 3 Andrey Loskutov CLA 2016-07-22 03:32:53 EDT 
Just tested with the 4.6.0 SDK, everything works. How do you specify the JVM for Eclipse? Do you have multiple JRE installations? What is JAVA_HOME saying?
Comment 4 Yannis Kargakis CLA 2016-07-22 04:46:45 EDT 
Hello,
I tried to 4.6.0 but the behavor is the same. I have totally removed old JRE installations. JVM for eclipse has been defined on eclipse.ini as: 

-vm
C:\Developer\tools\Java\jdk1.8.0_102\bin\javaw.exe

JAVA_HOME: C:\Developer\tools\Java\jdk1.8.0_102
Comment 5 Yannis Kargakis CLA 2016-07-22 04:48:33 EDT 
I think that somehow the problem is related with Bug 266651
Comment 6 Andrey Loskutov CLA 2016-07-22 05:07:21 EDT 
(In reply to Yannis Kargakis from comment #5)
> I think that somehow the problem is related with Bug 266651

SO it should not appear if you test with new workspace? So please, try to reproduce it with a clean Eclipse 4.6.0 install and a new workspace.
Comment 7 Yannis Kargakis CLA 2016-07-22 05:28:07 EDT 
(In reply to Andrey Loskutov from comment #6)
> (In reply to Yannis Kargakis from comment #5)
> > I think that somehow the problem is related with Bug 266651
> 
> SO it should not appear if you test with new workspace? So please, try to
> reproduce it with a clean Eclipse 4.6.0 install and a new workspace.

Unfortunately nothing :(
I have reinstalled java, used a clean Eclipse 4.6.0 with a new workspace
Comment 8 Sarika Sinha CLA 2016-07-25 02:06:49 EDT 
What was the previous version of Java being used ?
Comment 9 Eclipse Genie CLA 2019-12-20 08:17:29 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.