redhat-developer / redhat-developer/vscode-java
Java version support is quite misleading
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Here you say that this extension "Supports code from Java 1.8 to Java 25". But since it is based on https://github.com/eclipse-jdtls/eclipse.jdt.ls if you read the details there, it says: "Supports compiling projects from Java 1.8 through 24".
So it is not clear if using Java 25 is safe now. The "code" is supported, but not "compiling" it?
When using gradle configured for Java 25 (with the code obtained from gradle init) I can compile and execute tests, but the "Problems" panel is full of
[{
"resource": ".../bugrep/app/src/main/java/org/example/App.java",
"owner": "_generated_diagnostic_collection_name_#5",
"code": "4195414",
"severity": 4,
"message": "Compiling for Java version '25' is not supported yet. Using '24' instead",
"source": "Java",
"startLineNumber": 1,
"startColumn": 1,
"endLineNumber": 1,
"endColumn": 2,
"origin": "extHost1"
}]
This is quite confusing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the extension's stated Java 1.8–25 support with the linked eclipse.jdt.ls support details and the reported Gradle Java 25 diagnostics. Update the relevant support wording so users can distinguish supported source code from supported compilation, and confirm that the resulting statement matches the Problems panel behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100