Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable overriding the maven executable path on workspace level #1055

Open
fmeyertoens opened this issue Nov 26, 2024 · 0 comments · May be fixed by #1056
Open

Enable overriding the maven executable path on workspace level #1055

fmeyertoens opened this issue Nov 26, 2024 · 0 comments · May be fixed by #1056
Labels
good first issue Good for newcomers

Comments

@fmeyertoens
Copy link

Suggestion

Change the scope of the setting "maven.executable.path" from machine to machine-overridable?

vscode-maven/package.json

Lines 658 to 662 in 43618e6

"maven.executable.path": {
"type": "string",
"default": "",
"description": "%configuration.maven.executable.path%",
"scope": "machine"

Use Cases

Since the scope of the setting is machine it can only be set in the user settings and cannot be overridden for a specific workspace. When working on multiple projects (workspaces) with different maven versions it would be helpful if the path to the required maven executable could be set individually.

@fmeyertoens fmeyertoens changed the title Feature request Enable overriding the maven executable path on workspace level Nov 26, 2024
@testforstephen testforstephen added the good first issue Good for newcomers label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants