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

The "path" argument must be of type string. Received type undefined #277

Closed
LeonKwok0 opened this issue Mar 15, 2019 · 3 comments
Closed
Assignees
Labels
bug Something isn't working
Milestone

Comments

@LeonKwok0
Copy link

Describe the bug
i use macOS majove and maven 3.5.
i met the problem when i try to run the command maven.archetype.update through cmd+shift+p shortcut.
it mentioned me Command "maven.archetype.update" fails. The "path" argument must be of type string. Received type undefined

similar problem when i run maven.archetype.generate

Command "maven.archetype.generate" fails. Cannot read property 'length' of undefined returned through pop dialog

To Reproduce
Steps to reproduce the behavior:
i update my maven version. before that this extension works ok. i think it is this update recur problems . i use brew reinstalled maven.
but, i am sure that mvn command works ok in Terminal

Expected behavior

Environments (please complete the following information as much as possible):

  • OS: [macOS]
  • VS Code version: [1.32.3]
  • Extension version [0.15.0]
@Eskibear
Copy link
Member

It looks exactly the same issue with #274 .

Are you running the commands without any workspace or folder open? Open a folder first, see if the issue still exists. If it's gone, I suppose it's because of a potential NPE which is fixed by PR #276 but not released yet. Please let me know the result.

@Eskibear Eskibear self-assigned this Mar 15, 2019
@Eskibear Eskibear added the bug Something isn't working label Mar 15, 2019
@LeonKwok0
Copy link
Author

It looks exactly the same issue with #274 .

Are you running the commands without any workspace or folder open? Open a folder first, see if the issue still exists. If it's gone, I suppose it's because of a potential NPE which is fixed by PR #276 but not released yet. Please let me know the result.

thanks for your help. i opened a maven project created before and everything works ok ....

@Eskibear Eskibear added this to the 0.15.1 milestone Mar 15, 2019
@Eskibear
Copy link
Member

v0.15.1 has been released with the fix.

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

No branches or pull requests

2 participants