Skip to content

Require Java 21 or newer in parent POM for core and core components#781

Merged
timja merged 1 commit intojenkinsci:masterfrom
uhafner:java21
Jan 1, 2026
Merged

Require Java 21 or newer in parent POM for core and core components#781
timja merged 1 commit intojenkinsci:masterfrom
uhafner:java21

Conversation

@uhafner
Copy link
Member

@uhafner uhafner commented Jan 1, 2026

As Java 25 is available for a couple of months now, it is time to drop support for Java 17. Starting with this commit, Jenkins supports only Java 21 and 25, or newer.

See https://www.jenkins.io/blog/2023/11/06/introducing-2-2-2-java-support-plan/.

Followup for jenkinsci/jenkins#26018.

As Java 25 is available for a couple of months now,
it is time to drop support for Java 17. Starting with this commit, Jenkins supports only Java 21 and 25, or newer.

See https://www.jenkins.io/blog/2023/11/06/introducing-2-2-2-java-support-plan/.
@uhafner uhafner changed the title Require Java 21 or newer Require Java 21 or newer in parent POM for core and core components Jan 1, 2026
@timja timja merged commit 4565db3 into jenkinsci:master Jan 1, 2026
2 checks passed
@MarkEWaite
Copy link
Contributor

MarkEWaite commented Jan 1, 2026

Could we also change the major number on the release so that the breaking change is visible in 2.x pom versions?

@NotMyFault NotMyFault mentioned this pull request Jan 1, 2026
6 tasks
@NotMyFault
Copy link
Member

Could we also change the major number on the release so that the breaking change is visible in 2.x pom versions?

Covered in #783

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants