Skip to content
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

Open
StephenOTT opened this issue Jan 10, 2023 · 8 comments

Comments

@StephenOTT
Copy link

StephenOTT commented Jan 10, 2023

Describe the bug

https://docs.kogito.kie.org/latest/html_single/#con-runtime-tools-dev-ui_kogito-developing-process-services

Gradle:

    implementation 'io.quarkus:quarkus-arc'
    implementation 'org.kie.kogito:kogito-quarkus-processes'
    implementation 'org.kie.kogito:runtime-tools-quarkus-extension'

    implementation 'io.quarkus:quarkus-resteasy-reactive'
    implementation 'io.quarkus:quarkus-resteasy-reactive-jackson'

receive build error:

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.15.2.Final
  - io.quarkus:quarkus-resteasy::jar:2.15.2.Final
capability io.quarkus.rest.jackson is provided by:
  - io.quarkus:quarkus-resteasy-jackson::jar:2.15.2.Final
  - io.quarkus:quarkus-resteasy-reactive-jackson::jar:2.15.2.Final

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 or ver

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 or gradlew --version)

No response

Additional information

No response

@radtriste
Copy link
Contributor

@StephenOTT runtime-tools-quarkus-extension is bringing the quarkus-resteasy and quarkus-resteasy-jackson libraries as compile deps: https://github.com/kiegroup/kogito-apps/blob/main/runtime-tools-quarkus-extension-parent/runtime-tools-quarkus-extension/pom.xml

@StephenOTT
Copy link
Author

@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

@radtriste
Copy link
Contributor

@hbelmiro
Copy link
Contributor

Kogito doesn't support RESTEasy Reactive. Your application must use RESTEasy Classic.

@StephenOTT
Copy link
Author

Would this issue be solved by quarkusio/quarkus#19868 (comment) ?

@cristianonicolai
Copy link
Contributor

@paulovmr @pefernan

@spolti
Copy link
Member

spolti commented Jan 11, 2023

just found this issue https://github.com/kiegroup/kogito-runtimes/pull/1757 that enables reasteasy reactive.

@pefernan
Copy link
Contributor

Hi guys, that's because the extension is using quarkus-resteasy to define some custon REST endpoints. I think I have an idea on how to remove those endpoints by using the quarkus apis but I'll need some time to do some tests before moving forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

6 participants