Revert "[SEDONA-551] Upgrade GeoTools dependency to 31.0 for Apache SIS integration and Drop Java 8 support (#1382) #1408
Conversation
This file contains 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
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.
This reverts commit e0aabe3.
Did you read the Contributor Guide?
Is this PR related to a JIRA ticket?
What changes were proposed in this PR?
In the past weeks, we have collected feedback from the Sedona community and it turns out that 90% of Sedona users are still on Java 8. This is mainly because they all use fully managed cloud platforms such as AWS Glue and AWS EMR. It is not possible for them to upgrade the JVM themselves.
If we upgrade to Java 11 now, it will directly affect 90% of our users. Therefore, We have decided to revert the GeoTools 30.X upgrade and stay on 28.X. Hopefully, the major cloud platforms will start to support Java 11 in the next 6 months and then we will revisit this decision.
How was this patch tested?
Passing existing tests
Did this PR include necessary documentation updates?