Eli Bishop

Thanks. We should be able to put out a patch release shortly.

Fixed in the 5.10.1 release.

The current architecture doesn't allow switching horses in midstream like that. Something similar has been suggested in the past (either for this SDK or another one, I'm not sure) and...

Thanks for bringing this up. We've been slow in getting to Java 17 compatibility updates, and we need to give some more thought to how to get the module info...

Right, we need it but as you saw in your PR, the question is how to correctly update our somewhat complicated Gradle build to make sure it is actually generated...

For reproducibility, can you provide an example of a minimal project that uses the Java SDK as a dependency and fails to build because of this issue? It would also...

I ask because— 1. We're not really Java application developers; we build library code which by nature has to use a minimal feature set to remain compatible with an old...

> There's something in the Shadow Jar task that is generating a module-info.class with improper data. Well, I definitely see the incorrect module-info.class file. When decompiled, it looks like this:...

> I think that rules out the idea that the Shadow plugin is the cause, because we're not using Shadow for the "thin" jar. Sorry, correction - I am _not_...

@driverpt Could you please retest with the new 5.6.6 release? I fixed the Shadow problem that was causing that bad file to be included - so now there is _no_...