Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

JDK Requirements should clarify that java 8 requires a jre, not a jdk

Open
#1,300 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
java
Domain
documentation

Research direction

Open the linked JDK-Requirements wiki page and review the example configuration for Java 8. Clarify the required runtime type so it matches the working setup described in the issue, then verify that the instructions no longer direct users toward an incompatible path.

Written by the indexing model from the issue text.

Description

ai-triaged documentation jdk question

https://github.com/redhat-developer/vscode-java/wiki/JDK-Requirements documents how to set the project JDK. The example config contains "path": "/path/to/jdk-8". However, when I followed the instructions and entered a path to a JDK, I got an error that the jdk did not fulfill the requirements of "JavaSE-1.8". When I instead downloaded a jdk8 jre and pointed to it, everything worked. So I think the documentation should more clearly state that you need a JRE, not a JDK, for java 8.

Environment
  • Operating System: Ubuntu Linux
  • JDK version: 8
  • Visual Studio Code version: 1.75.1
  • Java extension version: Language Support for Java(TM) by Red Hat v1.15.0
  • Java Debugger extension version: Debugger for Java v0.48.0
Steps To Reproduce
  1. Follow instructions in https://github.com/redhat-developer/vscode-java/wiki/JDK-Requirements to configure a java 8 jdk as the default
  2. Observe error "Runtime at '/path/to/jdk1.8.0_xxx' is not compatible with the 'JavaSE-1.8' environment"
Dominant language
TypeScript
Stars
591
Forks
429
Avg merge
1d 9h
Merged PRs (30d)
19

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-java-debug

All issues in microsoft/vscode-java-debug

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.