build(ci): build using a java 11 toolchain #4927
Merged
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
Note this is not yet changing the compatibility level. This is setting up the build environment to make sure it can use java 11 first.
github-actions
bot
added
the
Category: Build/CI
1 task
jdrueckert
approved these changes
Nov 5, 2021
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.
Note this is not yet changing the compatibility level. This is setting up the build environment to make sure it can use java 11 first.
As this changes only the Jenkinsfile, it has no impact on local development environments. Our guide for setting up a development workspace has already recommended using Java 11 for a while now.
Requires
Because modules depend on engine, I expect things will go smoother if the module-building environment is Java 11-enabled before we start publishing Java 11 engine builds.