Skip to content

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

@dxps

Description

@dxps

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.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions