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

Bug 576139

Summary: [18] Java 18 support in JDT UI
Product: [Eclipse Project] JDT Reporter: Noopur Gupta <noopur_gupta>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3 CC: kalyan_prasad, loskutov
Version: 4.22   
Target Milestone: BETA J18   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 576140, 579013    
Bug Blocks:    

Description Noopur Gupta CLA 2021-09-21 05:13:23 EDT 
Root bug for JDT UI Java 18 support.
Comment 1 Andrey Loskutov CLA 2021-09-21 05:22:56 EDT 
I wonder if we can change the way how this future Java support is developed.

The way how development happens (on dedicated branch, not on master, not tested well by anyone till the release) is against the common Eclipse development rules. We see all the regressions and missing pieces too late. 

I know the main reason to do so were some licensing issues with Oracle Java pre release builds or something like this. I don't have the link to that, would be good to know the reason. 

I wonder if that these restrictioms are still valid and if yes, if we simply should provide new builds that support new Java releases few months later, so that all the new changes happen on master, used and tested by all who tests SDK  nightly builds etc.
Comment 2 Noopur Gupta CLA 2021-09-23 04:21:19 EDT 
(In reply to Andrey Loskutov from comment #1)
New Java support development takes 6 months in beta and the JDT project is in a state of flux during that time so developing in master will not work out. 

Also, we have regular Y-builds and P-builds once the development is in a decent state which can be used by anyone to test and provide feedback.