JDT/Plan/4.10
Planning page for JDT for 4.10
This page discusses target fixes and improvements to the Eclipse Java Development Tools for the 4.10 release.
Core
Java 11 Support
Java 11 support is integrated in 4.10 - Java 11 Tree.
Java 12 Support
Java 12 support will be integrated post 4.10 - Java 12 Tree Periodic patch builds of Beta quality will be delivered as P-builds applicable on top of 4.10 at a later date Product quality Java 12 support will be delivered post 4.10 (over 4.11)
Technical Debt and Enhancements
All Open Bugs All Resolved Bugs
A Java Versions' Perspective
For a Java releases driven planning refer Java Releases Support Page
UI
Java 12 Support
Moved to 4.11
Add Java 12 support - bugs.
Java 12 support will be added to a BETA branch until Java 12 goes GA.
Java 11 Support
Done
Add Java 11 support - bugs.
Java 11 support from the BETA branch will be integrated into the master branch for Eclipse 4.10 when Java 11 goes GA.
JUnit 5.3.1 Support
Done
Update to JUnit 5.3.1 - bug 536354.
JDT is expected to update to JUnit 5.3.1 for Eclipse 4.10.
Enhance support for JUnit 5
Done
Fix bugs and enhancements listed here.
Enhance support for Java 11
Done
Fix bugs and enhancements listed here.
Enhance support for Java 10
Done
Fix bugs and enhancements listed here.
Enhance support for Java 9
Done
Fix bugs and enhancements listed here.
Modularity support - Revisit/revamp the UI for supporting all module options in a better way.
Routine Maintenance and Enhancements
Done
Other bugs and enhancements.
Debug
Java 12 Support
Working on Java 12 support is one of the primary focus for 4.10. Java 12 is ongoing during 4.10 and will be delivered via Marketplace once Java 12 goes GA.
- JDT Debug Plan to support debugging in Java 12.
Moved to 4.11.
Java 11 Support
Working on Java 11 support is the primary focus for 4.9. Java 11 is ongoing during 4.9 and will be delivered via Marketplace once Java 11 goes GA.
- JDT Debug Plan to support debugging in Java 11.
Delivered in 4.10 M1.
Enhancing Lambda debugging user experience
Debugger stopped in a lambda expression cannot see variables in enclosing scope bug 538899
Delivered in 4.10 M1.
Lambda variable names in variables view is shown as arg$1 etc bug 534687
Moved out after analysis.
Enhancing Trigger Point user experience
Disabled trigger point gets enabled automatically bug 520346
Delivered in 4.10 M3.
Debugging user experience
Variables view: Add history with recent expressions to the details pane bug 334991
Moved out after analysis.
Routine Maintenance and Enhancements
Other Bugs and enhancements.