jena Bump com.esotericsoftware:kryo from 4.0.3 to 5.6.2

Bumps com.esotericsoftware:kryo from 4.0.3 to 5.6.2.

Release notes

Sourced from com.esotericsoftware:kryo's releases.

kryo-5.6.2

This is a maintenance release that recompiles 5.6.1 to restore compatibility with Java 8.

#1134 Recompile to ensure Java 8 support

Other Tasks:

Ensure release build can only happen with JDK 11

The full list of changes can be found here.

Many thanks to all contributors!

Upgrade Notes

For migration from previous major versions please check out the migration guide. We're asking the community to help and contribute this part: please edit the migration wiki page as you encounter any information or issues that might help others.

Compatibility

Serialization compatible

Standard IO: Yes

Unsafe-based IO: Yes

Binary compatible - Yes (Details)

Source compatible - Yes (Details)

kryo-5.6.1

DO NOT USE THIS VERSION

This version was accidentally targeted to Java 17. Use 5.6.2+ instead.

This is a maintenance release fixing wrong coordinates for the versioned artifact.

#1045 Re-add groupId to versioned POM

Other Tasks:

Fix deployment of snapshot builds

Upgrade Maven plugin dependencies

The full list of changes can be found here.

Many thanks to all contributors!

Upgrade Notes

For migration from previous major versions please check out the migration guide. We're asking the community to help and contribute this part: please edit the migration wiki page as you encounter any information or issues that might help others.

Compatibility

Serialization compatible

Standard IO: Yes

Unsafe-based IO: Yes

... (truncated)

Commits

fee6387 [maven-release-plugin] prepare release kryo-parent-5.6.2
a7a6504 #1134 Ensure that JDK 11 is used to build the release artifacts
6204b96 Bump junit.version from 5.11.1 to 5.11.2 (#1131)
36b7555 Bump org.apache.maven.plugins:maven-javadoc-plugin from 3.10.0 to 3.10.1 (#1133)
29d9101 Bump org.apache.maven.plugins:maven-surefire-plugin from 3.5.0 to 3.5.1 (#1132)
3dca694 Update README for 5.6.1
7261d15 Add compat report for 5.6.1
3d4beb1 [maven-release-plugin] prepare for next development iteration
7993436 [maven-release-plugin] prepare release kryo-parent-5.6.1
0de506b Bump org.apache.maven.plugins:maven-gpg-plugin from 3.2.6 to 3.2.7 (#1130)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Jun 16 '25 00:06 dependabot[bot]

The reason I used Kryo 4 instead of 5 is that Apache Spark (which we use with Jena) uses Kryo 4. I need to check whether by now perhaps the conflict I encountered back than has been resolved by shading on the Spark side.

The difference between the Kryo 4 and 5 APIs is just a generic <T> in some methods of the Serializer base class - but its an incompatible one :/

This is kryo on latest Spark 3:

Unfortunately, the new Spark 4 still relies on Kryo 4: https://mvnrepository.com/artifact/org.apache.spark/spark-core_2.13/4.0.0

This is kryo on on Spark 4:

Jun 19 '25 14:06 Aklakan

This comment states https://github.com/EsotericSoftware/kryo/issues/650#issuecomment-596249184

The versioned, self-contained artifact is now available as com.esotericsoftware.kryo:kryo5[...]

Maybe this artifact allows for mixing kryo 4 and 5 so that jena-geosparql could be upgraded to use https://central.sonatype.com/artifact/com.esotericsoftware/kryo5 However, it might break existing spatial indexes. If that's really the case than perhaps it would still be acceptable for jena6 though.

Sep 04 '25 19:09 Aklakan

I think when I tried the PR, Jena code didn't compile.

Sep 05 '25 13:09 afs

Yes, but if there is a (self-contained) kryo5 module that could be used alongside the kryo version used in apache spark, then for me there would be no problem to upgrade the code in jena-geosparql. I chose kryo 4 for compatibility.

Sep 05 '25 15:09 Aklakan

See #3425 (Kryo upgrade)

Sep 13 '25 20:09 afs

@dependabot recreate

Sep 25 '25 13:09 afs

Looks like com.esotericsoftware:kryo is no longer a dependency, so this is no longer needed.

Sep 25 '25 13:09 dependabot[bot]