redhat-developer / redhat-developer/vscode-java
maven.executable.options not being respected by vscode-java
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Hi. Most of the repositories that I work on need a specific profile and some other parameters.
I would need some specific mvn parameters only for vscode-java.
I don't want to create a .mvn because this would affect all mvn commands.
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
The report names the maven.executable.options setting and .mvn as the relevant entry points; start by tracing where vscode-java reads Maven options and invokes Maven. Done means the setting supplies parameters to vscode-java without requiring a repository .mvn file or changing other Maven commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100