Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when whitespace in project path #304

Closed
conscribtor opened this issue Apr 9, 2019 · 2 comments
Closed

Error when whitespace in project path #304

conscribtor opened this issue Apr 9, 2019 · 2 comments
Assignees
Labels
bug Something isn't working completed
Milestone

Comments

@conscribtor
Copy link

Describe the bug
When trying to open the MAVEN PROJECTS > Plugins tab within my project there is the following error message:

Spawn {"command":"mvn","args":["help:effective-pom","-Doutput=\"c:\\Users\\Mr Sinamun\\AppData\\Roaming\\Code\\User\\workspaceStorage\\7acaa3e44d8a285ba3a632c9cfa8f64b\\vscjava.vscode-maven\\2878fcfd49346ba9c689d26d3cf16622\"","-f","c:\\Users\\Mr Sinamun\\IdeaProjects\\ps_18_gruppe42\\pom.xml"]}
POM file c:\Users\Mr Sinamun specified the -f/--file command-line argument does not exist 

I think this happens because my project resides in a path with a space: ...\\Mr Sinamun\\....
This bug does not happen when the project is moved to c:\.

To Reproduce
Steps to reproduce the behavior:

  1. Open a Maven Project within a path with space. (e. g. C:\Users\Mr Sinamun\myproject)
  2. Go to 'Maven Projects'
  3. Click on 'Plugins'
  4. See error

Expected behavior
The MAVEN PROJECTS > Plugins tab should open even when the project resides in a path with a space.

Environments

  • OS: Windows 10
  • VS Code version: 1.33 (user setup)
  • Extension version 0.16.0
  • Maven 3.6.0
@conscribtor conscribtor changed the title Whitespace not escaped in project path Error when whitespace in project path Apr 9, 2019
@Eskibear Eskibear added the bug Something isn't working label Apr 10, 2019
@Eskibear Eskibear self-assigned this Apr 10, 2019
@Eskibear Eskibear added this to the 0.16.1 milestone Apr 10, 2019
@Eskibear
Copy link
Member

the fix has been shipped with v0.16.1, please have a try.

@conscribtor
Copy link
Author

It now works perfectly - Thank you for your work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working completed
Projects
None yet
Development

No branches or pull requests

2 participants