Bug 567224 - upgrade 4.16 to 4.17 doesn't warn about running on jdk8
Summary: upgrade 4.16 to 4.17 doesn't warn about running on jdk8
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.16   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-21 15:45 EDT by Andrej Kvasnica CLA
Modified: 2020-11-01 11:39 EST (History)
2 users (show)

See Also:

Attachments
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 Andrej Kvasnica CLA 2020-09-21 15:45:23 EDT 
issue debated at https://twitter.com/mickaelistria/status/1308122658677100544

Running Eclipse on jdk8, the upgrade from 4.16 to 4.17 runs and there was no warning about incompatible java runtime (jdk8). After upgrade and restart the Eclipse was not able to open dialogs and after quitting it wasn't able to start on jdk8 at all.

The incompatibility with jdk8 was not alerted.

How to reproduce:
1. download fresh eclipse 4.16 http://ftp-stud.fht-esslingen.de/pub/Mirrors/eclipse/technology/epp/downloads/release/2020-06/R/eclipse-java-2020-06-R-linux-gtk-x86_64.tar.gz
2. unzip / start eclipse using jre8
3. Check the Preferences > Install/Update > Verify...JRE is checked
4. Check for updates OR Install new software Eclipse Platform 4.17
5. Next> Remediation Page:Next>Install Details:Next>Review Licenses:Accept:Finish
6. No JRE alert at all.
7. Installing Software...
8. Restart.
9. Splash shows 2020-06
10. Package explorer: Broken (Could not create the view)
11. Restart. Splash shows 2020-06.
12. Package explorer still broken.
13. Quit.
14. Starting again. "Version 1.8.0_162 of the JVM is not suitable for this product. Version: 11 or greater is required."
15. Close.

fixing this:

1. Putting -vm \n jdk11 path into eclipse.ini
2. Starting again.
3. Splash shows 2020-09
4. everything is OK
Comment 1 Mickael Istria CLA 2020-09-21 15:48:43 EDT 
I'll need to verify it, but my first guess is that the remediation page shouldn't show in that case: a failure to resolve compatible JRE should abort the installation and ignore remediation.