bharos opened a new pull request, #13289: URL: https://github.com/apache/gravitino/pull/13289
### What changes were proposed in this pull request? Exclude `org.wildfly.openssl:wildfly-openssl` from the AWS and Azure shaded bundles. Remove the AWS relocation for that excluded provider, so an explicitly installed provider can use its original package. Document the TLS behavior and add two focused tests in each bundle module. ### Why are the changes needed? The bundles currently include WildFly OpenSSL 1.1.3.Final, including `DirectByteBufferDeallocator`, whose [source header specifies LGPL-2.1-or-later](https://github.com/wildfly-security/wildfly-openssl/blob/1.1.3.Final/java/src/main/java/org/wildfly/openssl/util/DirectByteBufferDeallocator.java). This is bundled implementation code, not just an optional dependency declaration. The [ASF third-party license policy](https://www.apache.org/legal/resolved.html#category-x) does not permit including it in the release. Related to #12755. This separates the provider exclusion from the Maven legal-document corrections in #13257 and can be reviewed and merged independently. ### Does this PR introduce _any_ user-facing change? The bundles use JSSE without the optional provider. Users explicitly selecting Hadoop's `OpenSSL` mode must install a compatible provider separately. No new configuration keys or public APIs. ### How was this patch tested? On JDK 17, the AWS and Azure bundle tests passed: each checks the actual shaded JAR for WildFly implementation entries and loads Hadoop's TLS factory in an isolated classloader. AWS's default JSSE mode initializes successfully; Azure's default mode falls back to JSSE. Spotless and RAT also passed. ```shell ./gradlew :bundles:aws-bundle:test :bundles:azure-bundle:test -PskipITs ./gradlew :bundles:aws-bundle:spotlessCheck :bundles:azure-bundle:spotlessCheck rat ``` These tests cover packaging and TLS factory initialization, not live cloud requests or compatibility with separately installed providers. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
