Rio JSON LD Jackson core/databind dependency problem about rdf4j

[hmottestad]

I think this might be due to the jsonld module importing the query module as a test dependency, which contains databind.

Btw. RDF4J 5.0.0 will hopefully use Titanium JSON-LD, which doesn't use jackson.

[vorburger]

My project uses https://bazel.build/ instead and it's theoretically possible Bazel is interpreting some dependency differently than Maven or Gradle.

Actually, strike that - I doubt that's the cause. Because rdf4j-rio-jsonld only declares a dependency on jackson-core, not jackson-databind, so this does seem odd, no?

It may will be some dependency mess bug ultimately more rooted in the "upstream" https://github.com/jsonld-java/jsonld-java than here, of course - but I thought I would still make a start here, first.

[hmottestad]

@vorburger I'm trying to track down the cause of this issue and I see that jsonld-java depends on jackson-databind, so rdf4j-rio-jsonld should include this transitively. Any chance you can provide a minimal example project that reproduces the bug?

[vorburger]

Btw. RDF4J 5.0.0 will hopefully use Titanium JSON-LD, which doesn't use jackson.

Good to know! FYI I'm on 5.0.0-M2, and happy to upgrade to try it.

I'm trying to track down the cause of this issue and I see that jsonld-java depends on jackson-databind, so rdf4j-rio-jsonld should include this transitively. Any chance you can provide a minimal example project that reproduces the bug?

Thank You! But as my project uses https://bazel.build and it's very well possible Bazel is interpreting some dependency differently than Maven or Gradle. (It's technically not "Bazel" but https://github.com/bazelbuild/rules_jvm_external, which internally uses https://get-coursier.io.) I doubt you have any interest in tracking down a problem that may well be very specific to that? As I've been able to locally solve the problem, unless you want to further dig into this for other reason, let's perhaps just close as not planned? Fine for me!