Skip to content

Enable overriding the maven executable path on workspace level #1055

@fmeyertoens

Description

@fmeyertoens

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions