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

Switch CI pipeline to a JDK17 baseline #27409

Closed
bclozel opened this issue Sep 15, 2021 · 0 comments
Closed

Switch CI pipeline to a JDK17 baseline #27409

bclozel opened this issue Sep 15, 2021 · 0 comments
Assignees
Labels
type: task A general task
Milestone

Comments

@bclozel
Copy link
Member

bclozel commented Sep 15, 2021

As announced on the spring.io blog, Spring Framework 6.0 will require JDK17 as a baseline.

As a result, the default build pipeline should use JDK17 (with future variants for JDK18+) and the published artifacts should use the Java 17 language level.

This task should refactor the current CI pipeline to:

  • only ship 17+ JDKs in the CI container image
  • consistently use Java 17 language level for compiling main and test sources
  • for now, Kotlin doesn't officially support Java 17, so we'll move to JDK 11 for now
@bclozel bclozel added the type: task A general task label Sep 15, 2021
@bclozel bclozel added this to the 6.0 M1 milestone Sep 15, 2021
@bclozel bclozel self-assigned this Sep 15, 2021
lxbzmy pushed a commit to lxbzmy/spring-framework that referenced this issue Mar 26, 2022
This commit introduces a new `spring-framework-6.0.x` CI pipeline with
JDK 17 baseline.

Note that Kotlin still uses a JDK11 baseline for now, this will be
addressed in spring-projectsgh-27413.

Closes spring-projectsgh-27409
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

No branches or pull requests

1 participant