Hello all
Note that shaded JAR files are incompatible with Java Platform Module
System (JPMS), because we cannot have multiple module-info.class files
in a single JAR file. This is not an issue as long as Sedona does not
have dependencies that are JPMS modules, or otherwise as long as the
modular dependencies apply some workaround for making possible to run on
the class-path (e.g. duplicating module-info.class information into
META-INF/services). But there is a possibility that some days, it will
not work anymore or would be very hard (e.g. merging all
module-info.class files into a single one may be difficult). It may be
safe to plan a transition from shaded JAR to unshaded ones, not
necessarily in this release but for the future.
Martin
Le 2023-10-10 à 19 h 29, Jia Yu a écrit :
The unshaded jars created lots of confusion for the users. People who
directly use the precompiled jars (due to no external internet
connection / no Maven resolvers) should use the shaded jars, rather
than the unshaded jars. A couple of users in the past just put all
shaded/unshaded jars in SPARK_HOME/jars which will break the
environment.
Therefore, I decided to remove all unshaded jars in the released
binary. If someone really wants to use the unshaded jars, they should
use the Maven coordinate together with a Maven dependency resolver. We
will still release those unshaded jars to Maven Central but just not
to ASF release binary.
In addition, ASF's voting process is mainly focused on voting the
source code. Binary is just a convenience release for users, no hard
requirements on it.
Please let me know if this makes sense to you. Or, if you have
suggestions, please also advise.
Thanks,
Jia
