redhat-developer / redhat-developer/vscode-java

feature request: select java runtime in vs code settings

Open
#1,684 4 comments 0 reactions 1 assignee View on GitHub

@testforstephen is already working on this.

Since Dec 18, 2020.

preferences
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

The current state of Java runtime support seems to be:

  • this extension needs Java 11
  • you can specify available runtimes in java.configuration.runtimes
  • however you can't specify/force which of these versions to use in a project; instead there's some auto detection that looks into eclipse/maven/gradle config

As we see in #1543 a lot of people are not happy with this situation. Me neither. Please add runtime selection in VS Code settings, so that one can force the usage of e.g. JavaSE-1.8 per workspace or even per directory.

Environment
  • Operating System: Windows 10
  • JDK version: OpenJDK 11 and Corretto JDK 8
  • Visual Studio Code version: 1.50.1
  • Java extension version: redhat.java v0.69.0, vscjava.vscode-java-pack v0.10.0
Steps To Reproduce
  1. install JDK 8
  2. install JDK 11 (-> system default)
  3. open vs code
  4. open a Java project and try to build it with JDK 8 (without changing java.home, because VS Code Java extension requires JDK 11)
Current Result

autodetection might work if eclipse/mvn/gradle settings are found that specify Java 8, otherwise JDK 11 is being used

Expected Result

usage of JDK 8 can be forced by VS Code settings per workspace or per directory

Additional Informations

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.