Quarkus CLI 3.25 unable to find mvn command (when no ./mvnw)

[nikkovacevic]

Describe the bug

I'm using Quarkus CLI 3.25.0 to update my project from 3.15 to 3.20. I have been doing it version by version by incrementing --stream parameter from 3.16 to 3.17 to 3.18 and so on. After trying quarkus update --stream=3.19, I get an error unable to find the maven executable.
It is in my path, maven home is also set, mvn -v returns 3.9.6 and where mvn returns correct location.

Expected behavior

`quarkus update --stream=3.19' would update the project to 3.19 as it did for versions before.

Actual behavior

quarkus update --stream=3.19 returns this error:

[ERROR]  Unable to find the maven executable, is it in your path?
[ERROR]  Unable to run Quarkus project update : Unable to find mvn command

quarkus update --stream=3.19 -e -- verbose returns this error:

[ERROR]  Unable to find the maven executable, is it in your path?
java.lang.RuntimeException: Unable to find mvn command
        at io.quarkus.devtools.exec.Executable.findExecutable(Executable.java:40)
        at io.quarkus.cli.build.ExecuteUtil.findExecutable(ExecuteUtil.java:30)
        at io.quarkus.cli.build.MavenRunner.getExecutable(MavenRunner.java:68)
        at io.quarkus.cli.build.BuildSystemRunner.prependExecutable(BuildSystemRunner.java:64)
        at io.quarkus.cli.build.MavenRunner.updateProject(MavenRunner.java:191)
        at io.quarkus.cli.Update.call(Update.java:25)
        at io.quarkus.cli.Update.call(Update.java:11)
        at picocli.CommandLine.executeUserObject(CommandLine.java:2031)
        at picocli.CommandLine.access$1500(CommandLine.java:148)
        at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2469)
        at picocli.CommandLine$RunLast.handle(CommandLine.java:2461)
        at picocli.CommandLine$RunLast.handle(CommandLine.java:2423)
        at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
        at picocli.CommandLine$RunLast.execute(CommandLine.java:2425)
        at picocli.CommandLine.execute(CommandLine.java:2174)
        at io.quarkus.cli.QuarkusCli.run(QuarkusCli.java:120)
        at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:141)
        at io.quarkus.runtime.Quarkus.run(Quarkus.java:80)
        at io.quarkus.runtime.Quarkus.run(Quarkus.java:51)
        at io.quarkus.cli.Main.main(Main.java:9)

[ERROR]  Unable to run Quarkus project update : Unable to find mvn command

How to Reproduce?

I cannot show you the project since its from work, but if I need to provide anything additionally let me know.

Output of uname -a or ver

No response

Output of java -version

21.0.1

Quarkus version or git rev

3.18.4

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.9.6

Additional information

It seemed to work yesterday (29.7. 2025) fine, but this morning I get this error. When trying the command on coworkers laptop with CLI 3.25.0 installed, he gets the same error.

Thanks for the help

[quarkus-bot]

/cc @ebullient (cli), @iocanel (cli)

[ia3andy]

I reproduced this issue and it affects all maven commands from the Quarkus CLI.

I am debugging

[ia3andy]

Fix will be in next release, please use Quarkus CLI 3.24 until then:

jbang app install --name quarkus --force https://repo1.maven.org/maven2/io/quarkus/quarkus-cli/3.24.5/quarkus-cli-3.24.5-runner.jar

[ia3andy]

This affects only projects without a maven wrapper (mvnw)

[ia3andy]

@nikkovacevic could you try the 3.24 (with this) and tell us if it works?

It might be a slightly different issue from the one I fixed

[gsmet]

@nikkovacevic actually, I think it's not the same issue than the one @ia3andy is chasing.

Could you tell us which OS you are using?

It would help if you could load the code from https://github.com/smallrye/smallrye-common in an IDE and set a breakpoint in https://github.com/smallrye/smallrye-common/blob/main/process/src/main/java/io/smallrye/common/process/ProcessUtil.java#L89 and see how it goes.

You can start the CLI in debug mode with:

JAVA_OPTS="-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:5005" quarkus dev

If you can have a look at what's going on and why it can't find your binary, that would be helpful.

[gsmet]

I deleted my first theory as it's incorrect so still very much interested in you trying to debug what's going on in ProcessUtil.