You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
dxps
changed the title
Debug startup comman to use mvnw or just mvn
Debug startup command to use mvnw or mvn
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):I would see it useful to consider using
mvn
instead ofmvnw
for such cases.I know that otherwise I could create my own (custom) task at the project level for such need.
The text was updated successfully, but these errors were encountered: