[VSCode extension] Add a folder-level setting to specify a custom Maven executable
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Description
Currently, all Maven invocations use a Maven installation that comes bundled with the extension. However, I'd like a folder-level setting to be able to specify a custom Maven executable to use.
Previous issue: https://issues.apache.org/jira/browse/NETBEANS-5409
### Use case/motivation
* allow working with projects that require a newer Maven version than the bundled one
* specify a particular Maven installation for projects that enforce a specific Maven version
* specify a legacy Maven installation for legacy projects
### Related issues
_No response_
### Are you willing to submit a pull request?
No
### Code of Conduct
Yes
Contributor guide
Research direction
No files or tests are named. Start by locating the VSCode extension's existing Maven executable selection and settings handling, then trace every Maven invocation. Done means a folder-level custom executable is used for the specified projects while the bundled Maven remains the default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100