-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build error from conflicting provider capabilities when using org.kie.kogito:runtime-tools-quarkus-extension with io.quarkus:quarkus-resteasy-reactive #2727
Comments
@StephenOTT |
@radtriste this seems like a bad design of that extensions deps, no? Other extensions do not seem to apply this passthrough. It would mean that someone adding this extension is then forced to modify their existing dependencies for something that is a dev ui function as per: https://docs.jboss.org/kogito/release/latest/html_single/#con-runtime-tools-dev-ui_kogito-developing-process-services |
Kogito doesn't support RESTEasy Reactive. Your application must use RESTEasy Classic. |
Would this issue be solved by quarkusio/quarkus#19868 (comment) ? |
just found this issue https://github.com/kiegroup/kogito-runtimes/pull/1757 that enables reasteasy reactive. |
Hi guys, that's because the extension is using |
Describe the bug
https://docs.kogito.kie.org/latest/html_single/#con-runtime-tools-dev-ui_kogito-developing-process-services
Gradle:
receive build error:
remove the resteasy deps and the error is removed.
Expected behavior
Would expect that you can use resteasy and runtime tools in the same project.
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: