eclipse-jdt / eclipse-jdt/eclipse.jdt.debug

Drop support for older Java versions in debugger

Open
#451 4 comments 1 reaction 1 assignee Claimed by @iloveeclipse View on GitHub
enhancement
Dominant language
Java
Stars
23
Forks
68
Avg merge
1d 4h
Merged PRs (30d)
13

Description

Same as https://github.com/eclipse-jdt/eclipse.jdt.ui/issues/1465 but for JDT Debug component.

We should follow-up the jdt.core issue https://github.com/eclipse-jdt/eclipse.jdt.core/issues/2536 with support in the JDT Debug as well. This issue is to discuss and track the corresponding debugger changes. To start with, we should remove the older versions of JEs and compliance levels from the UI.

The other issue that is kind of related but might be worth taking up is the ordering of the compliance levels. As we focus more on support for more recent Java versions, it doesn't make sense to stick to the older-versions-first approach on the UI drop down list. Perhaps, we should revert the order to reflect the trend in usage.

Example for the old EE's is properties of the JRE container on a project:

![image](https://github.com/eclipse-jdt/eclipse.jdt.debug/assets/964108/9cbc6c5d-49d0-43e4-bfc6-7f62ab80eac3)

also a "new Java project" and similar wizards:
![image](https://github.com/eclipse-jdt/eclipse.jdt.debug/assets/964108/04c9e91e-6d78-4f1a-81aa-fec937236ef3)

What is not clear for me if this page should also filter possible EE's (why should it if they can't be used for projects, but of course there are bundles around that have old EE's specified):

![image](https://github.com/eclipse-jdt/eclipse.jdt.debug/assets/964108/36be1ea9-b826-4f57-808e-08a4177dcbf7)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.