-
Notifications
You must be signed in to change notification settings - Fork 25k
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
[Gradle] Support runtime.java 24 and 25 #119387
Merged
elasticsearchmachine
merged 2 commits into
elastic:main
from
breskeby:support-runtime2425
Dec 31, 2024
Merged
[Gradle] Support runtime.java 24 and 25 #119387
elasticsearchmachine
merged 2 commits into
elastic:main
from
breskeby:support-runtime2425
Dec 31, 2024
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
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with -Druntime.java=24 -Druntime.java.build=29 which will resolve java ea24build29
breskeby
added
>non-issue
:Delivery/Build
Build or test infrastructure
Team:Delivery
Meta label for Delivery team
auto-backport
Automatically create backport pull requests when merged
v9.0.0
v8.17.1
v8.18.0
v8.16.3
labels
Dec 31, 2024
Pinging @elastic/es-delivery (Team:Delivery) |
breskeby
added
auto-merge-without-approval
Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!)
and removed
auto-backport
Automatically create backport pull requests when merged
labels
Dec 31, 2024
ChrisHegarty
approved these changes
Dec 31, 2024
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. LGTM
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes elastic#118329 (cherry picked from commit f028340)
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes elastic#118329 (cherry picked from commit f028340)
breskeby
added a commit
to breskeby/elasticsearch
that referenced
this pull request
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes elastic#118329 (cherry picked from commit f028340)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
elasticsearchmachine
pushed a commit
that referenced
this pull request
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes #118329 (cherry picked from commit f028340)
elasticsearchmachine
pushed a commit
that referenced
this pull request
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes #118329 (cherry picked from commit f028340)
elasticsearchmachine
pushed a commit
that referenced
this pull request
Dec 31, 2024
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes #118329 (cherry picked from commit f028340)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-merge-without-approval
Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!)
:Delivery/Build
Build or test infrastructure
>non-issue
Team:Delivery
Meta label for Delivery team
v8.16.3
v8.17.1
v8.18.0
v9.0.0
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.
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24)
By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25)
You can pass the build number also dynamically by running your build e.g. with
which will resolve java ea24 build 29
fixes #118329