Yan Zhang

Not related to Maven. Did you open this issue in the wrong repository?

#### For Maven executable settings > So relative paths, or an absolute path to a mvnw executable, are forbidden. Agree. > it simply walks up the parent folder hierarchy. This...

Then we have below actions to take: * [ ] improve the way to locate maven wrapper * walk through parent folders, looking for `mvnw` / `mvnw.cmd` (depending on which...

yes, I'll also update the description according to the changes.

Currently we directly parse output from `mvn dependency:tree`. The command failed because you didn't have the dependency (multi-module-library) installed into local maven repository. And the workaround is to run `mvn...

> I prefer not to do that because it's easy to forget to do.. I totally agree. We are looking for any efficiently way to calculate dependencies or your working...

> could there be an option added to the "Dependencies" node to expand all dependencies? At the moment you expand "Dependencies" menu, it already has information of *all* dependencies. But...

Maven commands requires a valid env JAVA_HOME to run. In your case, JAVA_HOME is set in terminal, but not available when executing background process. When executing background process, it inherits...

Current implementation uses `path` of the pom.xml as the identifier of a Maven project, instead of `uri`. It then reads the pom.xml file, and parses metadata from that. In Live...

Similar to #646 , so far the extension doesn't understand maven-specfic variables like `${maven.home}`, as we don't have a systematic way to resolve them. However, this extension is not responsible...