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

Debug startup command to use mvn if mvnw does not exist #95

Closed
dxps opened this issue Sep 26, 2019 · 0 comments · Fixed by #97
Closed

Debug startup command to use mvn if mvnw does not exist #95

dxps opened this issue Sep 26, 2019 · 0 comments · Fixed by #97
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@dxps
Copy link

dxps commented Sep 26, 2019

Hi everyone!

In a project where maven wrapper artifacts where removed for just cleanup/simplicity purposes, trying to use Quarkus: Debug current Quarkus project end up with (no surprize, of course):

> Executing task: ./mvnw quarkus:dev <

/bin/bash: ./mvnw: No such file or directory
The terminal process terminated with exit code: 127

Terminal will be reused by tasks, press any key to close it.

I would see it useful to consider using mvn instead of mvnw for such cases.

I know that otherwise I could create my own (custom) task at the project level for such need.

@dxps dxps changed the title Debug startup comman to use mvnw or just mvn Debug startup command to use mvnw or mvn Sep 26, 2019
@xorye xorye self-assigned this Sep 26, 2019
@fbricon fbricon added this to the 1.1.0 milestone Oct 3, 2019
@xorye xorye changed the title Debug startup command to use mvnw or mvn Debug startup command to use mvn if mvnw does not exist Oct 17, 2019
@fbricon fbricon added the enhancement New feature or request label Oct 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants