-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Support running on early-access JDK #18553
Conversation
Thank you for your pull request. |
CLA signed. |
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.
Thanks for your contribution! LGTM
@alluxio-bot recheck |
@YichuanSun thanks for the review! |
alluxio-bot, merge this please. |
merge failed: |
alluxio-bot, merge this please. |
@YichuanSun can you release new version? I'd like to start testing it with JDK 23-ea |
I don't really understand. Do you mean creating a new branch like "Alluxio-x.x.x-for-your-test"? |
I don't know how your automation works. I need 312 release |
I'm more confused, what is 312? Alluxio 3.1.2? Or anything else? |
Trino is currently using version 311 from mvncentral: https://mvnrepository.com/artifact/org.alluxio/alluxio-core-common/311 |
I see. Sorry I don't have the right to do this. |
Maybe you can find any help in our slack channel, version release is out of my scope, actually I don't know how to do so. |
What changes are proposed in this pull request?
Alluxio doesn't work with early-access (EA) JDKs which makes it hard to do some forward-testing before new JDK is released.
Why are the changes needed?
Please clarify why the changes are needed. For instance,
Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including