Istvan Toth created PHOENIX-7011:
------------------------------------
Summary: Remove relocated multi-version classes from shaded
artifacts
Key: PHOENIX-7011
URL: https://issues.apache.org/jira/browse/PHOENIX-7011
Project: Phoenix
Issue Type: Bug
Components: core
Reporter: Istvan Toth
This is a forward-looking ticket to track the problem, these shading issues are
not a burning problem yet.
Shading multi-release JARs, like jackson 2.15.1 has multiple problems:
* IT simply fails with our current maven-shade-plugin version in some cases.
This can be fixed by using the latest version, but that one is ~40% slower.
* The resulting JAR doesn't work as a multi-version JAR, because the directory
structure is not shaded. See MSHADE-406
For the current release, we have some versioned JARs from hbase-thirdparty, but
as those are already pre-shaded, they are not hit by MSHADE-406
I seem to recall that Java will sometimes load classes from the wrong
directory, so we could check whether those versioned classes are loaded despite
being in the wrong directory.
If not, we should consider filtering these classes from the META-INF/versions
directory, to avoid polluting the classpath with classes in invalid location,
at least until MSHADE-406 is fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
