CommandNotFoundException: No valid executable found

quality-focused-jay · November 17, 2023, 4:14pm

Stacktrace:

2023-11-17T13:40:12.117+01:00 ERROR 22572 --- [io-8080-exec-10] o.a.c.c.C.[.[.[/].[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [com.vaadin.flow.server.Service
Exception: java.lang.IllegalStateException: com.vaadin.flow.server.ExecutionFailedException: Failed to configure Hilla engine] with root cause

dev.hilla.engine.commandrunner.CommandNotFoundException: No valid executable found
at dev.hilla.engine.commandrunner.CommandRunner.lambda$run$0(CommandRunner.java:72) ~[engine-core-2.3.2.jar!/:na]
at java.base/java.util.Optional.orElseThrow(Optional.java:403) ~[na:na]
at dev.hilla.engine.commandrunner.CommandRunner.run(CommandRunner.java:72) ~[engine-core-2.3.2.jar!/:na]
at dev.hilla.internal.AbstractTaskEndpointGenerator.prepareEngineConfiguration(AbstractTaskEndpointGenerator.java:87) ~[engine-runtime-2.3.2.jar!/:na]
at dev.hilla.internal.AbstractTaskEndpointGenerator.getEngineConfiguration(AbstractTaskEndpointGenerator.java:59) ~[engine-runtime-2.3.2.jar!/:na]
at dev.hilla.internal.TaskGenerateOpenAPIImpl.execute(TaskGenerateOpenAPIImpl.java:73) ~[engine-runtime-2.3.2.jar!/:na]
at com.vaadin.flow.server.frontend.NodeTasks.execute(NodeTasks.java:312) ~[flow-server-24.2.0.jar!/:24.2.0]
at com.vaadin.base.devserver.startup.DevModeInitializer.runNodeTasks(DevModeInitializer.java:352) ~[vaadin-dev-server-24.2.0.jar!/:na]
at com.vaadin.base.devserver.startup.DevModeInitializer.lambda$initDevModeHandler$0(DevModeInitializer.java:293) ~[vaadin-dev-server-24.2.0.jar!/:na]

cheerful-baboon · November 17, 2023, 4:34pm

Looks like it can not find mvn on your PATH, or the mvnw wrapper in the current folder.

marcoc_753 · November 17, 2023, 4:44pm

I can see a similar issue on my environment when starting the application from the IDE and not having a maven wrapper (or having the Hilla application in a maven submodule, so the wrapper is in a parent folder)
This happens to me because, I have maven managed by sdkman so IDEA cannot find it in the PATH, as Sascha said

marcoc_753 · November 17, 2023, 4:46pm

Anyway, it would be nice to be able to provide an additional executable for MavenRunner as a system property

practical-rat · November 20, 2023, 8:47am

@versatile-zorse, if you can, please consider opening a ticket about sdkman incompatibility with Hilla.

marcoc_753 · November 20, 2023, 9:39am

github.com/vaadin/hilla

Allow MavenRunner to accept a custom path for maven executable

opened 09:39AM - 20 Nov 23 UTC

closed 10:54AM - 05 Dec 23 UTC

mcollovati

enhancement hilla prerelease version for Hilla 2.5.0 Released with Hilla 2.5.0.alpha12

### Describe your motivation Currently, to detect the maven executable Hilla us…es a list of potential executables hard-coded in `MavenRunner` class (e.g. for *nix they are `./mvnw` and `mvn`). However, the detection can fail when starting the Hilla application from and IDE, if Maven executable is not present on PATH. For example, if you use [SDKMAN!](https://sdkman.io/) to handle multiple maven installations, the default one may be added to the PATH in a way that is not visible. Another case of failure is having a multi-module maven project, where the Hilla application is in a submodule, but the maven wrapper is in the root project folder. ### Describe the solution you'd like It would be nice to have the opportunity to extend the maven executables path list in MavenRunner by using a system property and/or the MAVEN_HOME environment variable (e.g. $MAVEN_HOME/bin/mvn). ### Describe alternatives you've considered Setting a PATH environment variable in the IDE run configuration seems not to work. Also creating a symlink to the maven wrapper in the submodule is not working properly. ### Additional context _No response_

Fernando_Marino · March 17, 2025, 3:34pm

my two cent here. In my case I have a multi-module gradle project and the gradlew is at the top level, while the vaading application is one of the submodules

Luciano_Vernaschi · March 17, 2025, 3:56pm

Hi, this issue should be solved in Vaadin 24.7 as we no longer need to run Gradle or Maven at each code change.