Skip to content
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
merged 2 commits into from
Dec 31, 2024

Conversation

breskeby
Copy link
Contributor

@breskeby breskeby commented 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

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 breskeby requested a review from a team as a code owner December 31, 2024 12:23
@breskeby 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
@breskeby breskeby self-assigned this Dec 31, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

@breskeby 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
Copy link
Contributor

@ChrisHegarty ChrisHegarty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. LGTM

@elasticsearchmachine elasticsearchmachine merged commit f028340 into elastic:main Dec 31, 2024
17 checks passed
@breskeby breskeby deleted the support-runtime2425 branch December 31, 2024 14:06
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)
@breskeby
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.x
8.17
8.16

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for JDK EA builds in -Druntime.java=xx
3 participants