Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
quarkus-spring-web codestart can't be used with quarkus-resteasy-reactive
See original GitHub issueDescribe the bug
quarkus-spring-web codestart can’t be used with quarkus-resteasy-reactive
Caused by: java.lang.IllegalStateException: Please make sure there is only one provider of the following capabilities:
capability io.quarkus.rest is provided by:
- io.quarkus:quarkus-resteasy-reactive::jar:2.6.3.Final
- io.quarkus:quarkus-resteasy::jar:2.6.3.Final
quarkus-spring-web codestart forces RESTEasy Classic - https://github.com/quarkusio/quarkus/blob/main/independent-projects/tools/base-codestarts/src/main/resources/codestarts/quarkus/extension-codestarts/spring-web-codestart/codestart.yml#L19
Expected behavior
quarkus-spring-web codestart can be used with quarkus-resteasy-reactive
Actual behavior
quarkus-spring-web codestart can’t be used with quarkus-resteasy-reactive
How to Reproduce?
-
mvn io.quarkus.platform:quarkus-maven-plugin:2.6.3.Final:create -DprojectGroupId=my-groupId -DprojectArtifactId=app-generated-skeleton -DprojectVersion=1.0.0-SNAPSHOT -DpackageName=org.my.group -DquarkusRegistryClient=false -DplatformArtifactId=quarkus-bom -DplatformVersion=2.6.3.Final -Dextensions=quarkus-spring-web,quarkus-resteasy-reactive -
mvn -f app-generated-skeleton quarkus:dev
Output of uname -a or ver
No response
Output of java -version
Java 17
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.6.3.Final
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Pretty much yeah. 1 is the most important as the generated projects are broken ATM…
So this is the plan you are suggesting right?: 1- we create a PR to use resteasy-reactive-jackson instead (compat with resteasy will be temp broken) 2- we introduce the conditional dependencies 3- we remove resteasy-reactive-jackson from the codestart