Simplest generated project fails with quarkus:dev with JDK 13 on Windows 10
See original GitHub issueDescribe the bug
Generated project doesn’t run with quarkus:dev
on Windows 10. The same project run seamlessly on macOS Catalina.
Expected behavior Runs without any error.
Actual behavior Fails at run with error message:
[INFO] --- quarkus-maven-plugin:1.0.0.CR1:dev (default-cli) @ code-with-quarkus ---
Java HotSpot(TM) 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
Listening for transport dt_socket at address: 5005
Error: Could not find or load main class io.quarkus.dev.DevModeMain
Caused by: java.lang.ClassNotFoundException: io.quarkus.dev.DevModeMain
To Reproduce Steps to reproduce the behavior:
- Generate the simplest app on code.quarkus.io (whithout extensions)
- Run
mvn compile quarkus:dev
Environment:
- OS: Windows 10 (KO) and macOS Catalina (OK)
- JDK: tested with Oracle JDK 13
Additional context I found a similar issue: https://github.com/apache/camel-quarkus/issues/263 but this one seems related to camel and I am not using it.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Building Quarkus apps with Quarkus Command Line Interface ...
The quarkus command lets you create projects, manage extensions and do essential build and dev commands using the underlying project build tool.
Read more >quarkus 2.1.4 - mvnw quarkus:dev not working on windows 10
[ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:2.1.4.Final:dev (default-cli) on project hibernate-orm-quickstart: Execution ...
Read more >Failed to build quarkus application: - Google Groups
[ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:2.10.0.Final:build (default) on project document-management-service: Failed to build quarkus ...
Read more >Explore Java 17 language features with Quarkus
When you created the sample-app project using the Maven plugin, Dockerfiles were also generated in src/main/docker . However, those were ...
Read more >Creating a Simple Microservice with Quarkus and MongoDB
In the cloud era, we need speed and light-weight applications, Quarkus makes it possible masterfully. To start a Java application with Quarkus, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The JDK 13
Class-Path
details in thejar
spec[1] has additional details explaining what constitutes as validClass-Path
entries. Plus the linked mailing list thread makes it clear that this change is intentional. So I will try and come up with a fix to ourClass-Path
value generation to make it work against Java 13 as well as previous versions of Java.[1] https://docs.oracle.com/en/java/javase/13/docs/specs/jar/jar.html#class-path-attribute
I’ve proposed https://github.com/quarkusio/quarkus/pull/5808 to see if we would like to go with the approach suggested in that PR.