Open AlekHed opened 19 hours ago
Possible cause:
I see that those linked discussion mention multi-release jars... Could it be that the Nessie build packages them incorrectly?
I think it's rather the fact that the user is running Java 22, and dnsjava multi-release jars are broken for Java >= 18 it seems.
What happened
After updating nessie gc jar to version 0.100.0 started receiving error:
Interesting, that I have same problem if i try to run with same configs using docker run on official nessie gc 0.100.0 image.
How to reproduce it
run gc from shell:
Nessie server type (docker/uber-jar/built from source) and version
uber-jar/docker
Client type (Ex: UI/Spark/pynessie ...) and version
zsh
Additional information
Java:
OS: