update commons-lang3 version for Java 11 support #273
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I ran into an issue using resolvers with Java 11, and after some debugging I traced the issue to the Apache commons-lang3 library.
This issue only comes up when implementing a
GraphQLResolverclass - root resolvers, etc are fine.In
ResolverInfo.kt, theNormalResolverInfo::findDataClassmethod makes a call toTypeUtils.determineTypeArguments, which internally hits a NPE - as commons-lang3 3.8 and below improperly create an enum value representing the current Java version.By upgrading to 3.9 I have had success running my project again.
Thanks, hope this helps!