Yan Zhang
Yan Zhang
The “local repository” one is just a warning. Following the “spawn” one, there should be detailed output of the command, see if it’s successfully executed?
Maven isn't displaying the variable property containing the name of the artifact properly in VS Code
It's not reading from effective pom. Currently only `properties` are substituted. One approach is, whenever effective pom is calculated, we update the name from effective pom. Another one is, we...
Have you tried inspecting conflicts with Maven explorer? See below. 
> no filtering is implemented FYI VS Code itself implements basic filtering for all tree views, you can type some keywords when focusing on it. But I agree it would...
> When i debug a maven based java application in VSCode the dependencies which are defined in the "test-scope" are not loaded and therefore it is not possible to debug...
A command "Add Maven Wrapper" should work when there's no wrapper detected in project root. Source of the wrapper can be: #### Option 1: If a local `mvn` is found...
> VS Code Maven Extension already comes with a Maven bundled within. No. To clarify, a Maven **wrapper** (instead of a Maven distribution) is bundled in this extension. That was...
Yes. Option A) use bundled Maven Wrapper to call maven-wrapper-plugin to add the Maven Wrapper to a project. Option B) directly copy the bundled Maven Wrapper to a project. I...
BTW, here is a quick demo of this feature, triggered from command palatte. I'm thinking about whether we need more entries. https://user-images.githubusercontent.com/2351748/133648682-0ffac8c3-42d4-4d97-b2c6-d6ad158a9030.mp4
Agree to allow user input of Maven version.