feat: Add GraalVM native-image support by removing Guava shading #614
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The shaded Guava (split.com.google.common.*) causes GraalVM native-image parsing errors because it lacks the native-image configuration that standard Guava provides. Problem: When building a native image with the Split SDK, GraalVM fails with: Error parsing split.com.google.common.cache.LocalCache$Segment Caused by: Unresolved type split.com.google.common.util.concurrent.SettableFuture Root cause: The Maven Shade Plugin relocates Guava to split.com.google.common.* which strips the META-INF/native-image configuration that standard Guava includes for GraalVM compatibility. Solution: Remove Guava from the shade plugin configuration. Guava remains as a transitive dependency, allowing applications to use the standard Guava library which has proper GraalVM native-image support. Changes: - Remove com.google.guava:guava from shade plugin includes - Remove org.checkerframework:* from shade plugin includes - Remove com.google -> split.com.google relocation - Remove org.checkerframework -> split.org.checkerframework relocation Impact: - Guava is now a transitive dependency instead of being bundled - Applications using GraalVM native-image can now build successfully - Potential version conflicts with other Guava users (mitigated by dependency management in build tools) Tested with: - Quarkus 3.27.1 + Mandrel JDK-23 - Native image builds successfully - Split client works correctly at runtime
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR enables GraalVM native-image compilation for applications using the Split.io Java SDK.
Problem
The Split SDK shades Guava to
split.com.google.common.*to avoid dependency conflicts. However, this shaded Guava lacks the GraalVM native-image configuration that standard Guava provides, causing build failures:Root Cause
Standard Guava (
com.google.common.*) includes GraalVM native-image configuration inMETA-INF/native-image/. When the SDK shades Guava tosplit.com.google.common.*, this configuration is lost, and GraalVM cannot parse complex classes likeLocalCache.Segment.Solution
Remove Guava from the shade plugin configuration. Guava remains as a transitive dependency, allowing applications to use the standard Guava library which has proper GraalVM native-image support.
Changes
com.google.guava:guavafrom shade plugin includesorg.checkerframework:*from shade plugin includescom.google→split.com.googlerelocationorg.checkerframework→split.org.checkerframeworkrelocationTesting
Impact
Breaking Change
Applications that explicitly depend on the shaded Guava package names (
split.com.google.*) will need to update imports. However, this is unlikely since the shaded packages are internal implementation details.Benefits
Potential Risks
Related Frameworks
This fix enables Split SDK usage with:
Checklist