-
Notifications
You must be signed in to change notification settings - Fork 989
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade gradle5 jdk11 #1221
Upgrade gradle5 jdk11 #1221
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm running integration tests with some snapshots I made from the most recent ES revisions. I'll update here once they're complete. I have a suspicion that our supported versions of Hadoop will not want to play nice with the version updates, but it could be just paranoia.
} | ||
|
||
targetCompatibility = "8" | ||
sourceCompatibility = "8" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is quite the right place for this. We set target and source compatibility levels for the artifacts from within ES-Hadoop's BuildPlugin in the buildSrc directory. Unless I'm mistaken and this isn't meant to set that?
Integration tests are failing at the moment with these changes on the local build-tools snapshot. It's tripping up on some low level Hive + JDBC + JDO mess related to the newer java runtime. I know that there are some Hadoop incompatibilities as well from code that parses java versions in static blocks. We will have to modify the build to use different java runtimes for the tests like ES does. |
I think this should just be closed out at this point. Getting the build on to jdk 11 is going to require the removal of some older supported framework versions as they simply do not support running on top of java versions above jdk 8. Now that elastic/elasticsearch#36453 is merged, the build should pass once more. If we feel that this should still be discussed, then I'm fine with re-opening. Until then I'll close this out. |
build-tools now targets Java 10 ( class version 54 ).
Building with older versions of java no longer works,
while the build doesn't seem to apply the plugin it does uses classes form build tools like
VersionProperties
which can't be loaded when the build is ran with older JDKs.This PR makes it possible to build using java 11 while setting target version to 8 so it will still work on older JVMs (this is the oldest ES supports).
I'm not sure if this is the right target, We seem to support Spark
2.0+
which from a quick search seems to support java 7 up to2.2
.