[AMORO-3531][WIP] Support build project with JDK 8, 11 and 17 #3532
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
github-actions
bot
added
type:docs
xxubai
commented
Apr 25, 2025
klion26
reviewed
Apr 28, 2025
| - uses: actions/checkout@v3 | ||
|
|
||
| - name: Set up JDK 8 | ||
| - name: Set up JDK 11 |
Member
There was a problem hiding this comment.
Do we still need the CI of JDK8?
After the change, it seems that we can't guarantee that Amoro can still work on JDK8.
IIUC, we need to support running CI on both JDK8 and JDK11 when we start deprecating JDK8, and the CI of JDK8 can be removed when we no longer support JDK8.
xxubai
changed the title
xxubai
changed the title
xxubai
changed the title
3 tasks
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.
Why are the changes needed?
Close #3531
Brief change log
How was this patch tested?
Add some test cases that check the changes thoroughly including negative and positive cases if possible
Add screenshots for manual tests if appropriate
Run test locally before making a pull request
Documentation