Maven Class FireCommand Method Pass Environment Variables #228
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request started from the need to have environment variables from the system/shell in the child process spawned by the maven class firecommand method. I made a handful of other commits to get the project to compile. I couldn't get the npm test script to run, but that's because I'm developing in a dev container without x server. I packaged the extension, installed it locally, and confirmed the environment variables are available to the child processes as expected.
Reference Bug Report: VS Code Payara Tools Extension - Payara Micro Instance - Missing Environment Variables #91