Another release depending on kryo-shaded 4.0.2

[jzhuge]

Is it possible to push another release based on 0.43 with dependency kryo-shaded instead of kryo?

We are not ready for kryo v5 yet and prefer kryo-shaded to kryo in order to avoid conflicts of org.ow2.asm:asm.

[magro]

Could you exclude the dependency on kryo when depending on kryo-serializers? And depend on kryo-shaded explicitly?

[jzhuge]

Yes it works but it is the kind of thing (as well as custom Gradle dependency substitution strategy) I am trying to avoid.

[magro]

Sure. Let me see when I find the time for this.