Open
Description
Describe the bug
When I opened a Maven project, it would look for pom.xml
and download dependencies to my machine local repository which normally is ${user.home}/.m2/repository
. But when I change the local repository to ${maven.home}/repositories
in the setting.xml
VSCode would create a folder called ${maven.home}
in the working directory then put all dependencies inside it instead of the real ${maven.home}
To Reproduce
- Download maven from https://maven.apache.org/download.cgi
- Extract and set its binary folder to the PATH environment variable
- At the downloaded folder, go to
conf/settings.xml
- Add this piece into the setting tag
<localRepository>${maven.home}/repositories</localRepository>
- Open the VSCode setting page and set the global maven setting to the editted
settings.xml
above - Open any maven project and see the result
Expected behavior
VSCode would install dependencies in the real ${maven.home}/repositories
directory
Environments
- Edition Windows 10 Pro
- Version 21H1
- Installed on 2021-05-27
- OS build 19043.1110
- Experience Windows Feature Experience Pack 120.2212.3530.0
- VS Code version: 1.58.2
- Extension version v0.31.0
Screenshots
Workaround
Use absolute directory path in the settings.xml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment