redhat-developer / redhat-developer/vscode-java

Equivalent to java.test.config.env for launching java programs

Open
#3,016 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

There is java.test.config.env where one can set environment variables set for testing, however the same is missing for launching java programs. There is an env option using launch configurations, however since launch configurations are shared it cannot be used, e.g. with env variables pointing to local folders etc.

Environment
  • Operating System: Linux
  • JDK version: 17
  • Visual Studio Code version: 1.76.2
  • Java extension version: 1.13.0
Steps To Reproduce

There is no way to achieve the desired behaviour yet

Current Result

There is no way to achieve the desired behaviour yet

Expected Result

Environment variables can be set globally for java programs to run and will be mixed and merged with settings hierarchy global/user/workspace

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.

Research direction

Start by reading how java.test.config.env is defined and how launch configurations currently provide environment variables. Define done as a global setting for Java program launches that merges with the global, user, and workspace settings hierarchy while supporting local folder values.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript, vscode
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.