-
Notifications
You must be signed in to change notification settings - Fork 209
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
cannot resolve kie-addons-quarkus-tracing-decision dependency #3566
Comments
Hi @deepakkapoor23 : could you please include a minimal reproducer, i.e. a very trimmed down project that recreates the problem you are facing ? Thanks! |
kogito-reproducer.zip Uncomment the kie-addons-quarkus-tracing-decision dependency in settings.gradle and pom.xml files to see the issue. Commands: mvnw clean package -U gradlew clean build --no-build-cache |
Execution failed for task ':quarkusGenerateCode'.
|
Could this be because kogito-bom is missing an entry for kie-addons-quarkus-tracing-decision? |
Describe the bug
Build failure with tracing dependency included.
Failed to collect dependencies of org.kie:kie-addons-quarkus-tracing-decision-deployment:jar:999-SNAPSHOT: either its POM could not be resolved from the available Maven repositories or the artifact does not have any dependencies while at least a dependency on the runtime artifact org.kie:kie-addons-quarkus-tracing-decision:jar:999-20240522.100214-6 is expected
Expected behavior
Build should complete with assembly created.
Actual behavior
Build fails with above error as it cannot resolve the runtime dependency.
How to Reproduce?
Include following dependency and run maven build.
org.kie kie-addons-quarkus-tracing-decision 999-SNAPSHOTOutput of
uname -a
orver
Windows
Output of
java -version
17
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)
999-SNAPSHOT
Build tool (ie. output of
mvnw --version
orgradlew --version
)gradle 8.6
Additional information
No response
The text was updated successfully, but these errors were encountered: