You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
fmeyertoens
changed the title
Feature request
Enable overriding the maven executable path on workspace level
Nov 26, 2024
Suggestion
Change the scope of the setting "maven.executable.path" from
machine
tomachine-overridable
?vscode-maven/package.json
Lines 658 to 662 in 43618e6
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.The text was updated successfully, but these errors were encountered: