Closed lawcha closed 2 years ago
Hi Laurent, I think the root cause is that module ksml-query has a dependency on jakarta.ws.rs-api:3.0.0 and module ksml depends on the Confluent schema registry client which transitively depends on jakarta.ws.rs-api:2.1.6. Maven tries to resolve the conflict and in the runtime image only the 3.0.0 version is present. Unfortunately the package naming between the versions is slightly different and what is called javax.ws.rs.core.UriBuilder in 2.1.6 is called jakarta.ws.rs.core.UriBuilder in 3.0.0. (This is apparently due to some trademark discussion between the Eclipse foundation and Oracle).
To resolve either module ksml-query will have to be downgraded to use ws 2.1.6, or module ksml needs to be made to work with ws 3.0.0 (probably by upgrading the registry cient dependency). I've tried the former but did not manage to get it to build. (See also comment thread in #35 )
Hi, Okay, I see. Thank you for the explanation. Hopefully, I am not in a hurry to use KSML in my project. I am looking forward to an update. Does version 0.0.3 of KSML works well? I would like to try to understand how the given examples work until the current bug is solved.
I followed the Getting Started tutorial to run the first example YAML, but I get the following error when executing the
run.sh
file.Environment
Problem
The problem should come from the runner, as the logs of the producer seem good according to the Getting started.
Thank you for your help