If neither of the maven.executable.* settings then mvn is used without resolving via the PATH env var

[scottkurz]

This is a bit of a subtle point and I'm not sure how much it matters, or if it could even be considered a "good" thing in a way.

The LTV precedence for locating mvn/mvnw executable is:

1. Look for maven.executable.path setting
2. Look for maven.executable.preferWrapper setting and if set, look for mvnw
3. If still not found (whether 2. is set or not), just use 'mvn'.

See:

liberty-tools-vscode/src/liberty/devCommands.ts

Line 551 in c820efa

return "mvn";

This is a bit of a difference vs. vscode-maven,
https://github.com/microsoft/vscode-maven/blob/8ee1ef0bbe3810e96c161d0c0e6c7e72c9c54490/src/utils/mavenUtils.ts#L212
which resolves this "mvn" string to the PATH env var... IIUC.

The difference comes into play if you have a shell alias for 'mvn', for example...the LTV way will "work" but the vscode-maven will not.

Like I said.. could this be considered a good thing? Or is it somehow more dangerous to execute an alias? Not sure.

Thought I'd open the issue to make us aware of this in the meantime.