Create Java 17 + Spring Framework 6 + Jakarta EE 9 platform
Key details
Basics
Logistics
Basics
Logistics
Description
Environment
None
Subtasks
100% Done
Work | Priority | Story Points | Assignee | Status |
|---|---|---|---|---|
Ian Young Ian Young | ||||
Ian Young Ian Young |
Linked work items
is blocked by
Activity
Ian Young
October 24, 2022 at 10:29 AM
Rod Widdowson
October 22, 2022 at 3:12 PM
Rod Widdowson
October 21, 2022 at 2:00 PM
Rod Widdowson
October 21, 2022 at 1:24 PM
Rod Widdowson
June 24, 2022 at 1:03 PM
Completed
Details
Assignee
Ian Young
Ian YoungReporter
Ian Young
Ian YoungCreated September 8, 2021 at 2:56 PM
Updated October 24, 2022 at 10:29 AM
Resolved October 24, 2022 at 10:29 AM

We now know that Spring Framework 6 will be out at the end of 2023, that it will have a minimum requirement of Java 17 (but will support the next two LTS releases as well, Java 23 and Java 29) and will switch from the Java EE APIs to Jakarta EE 9, thus requiring namespace changes.
This issue is a placeholder to wrap tasks related to exploring that environment, including experimenting with building our software stack under a new platform POM based on the same components.
This will kick off with experimental branches of our projects once a milestone of Spring Framework 6 is available, expected before the end of 2021.
The expectation is that we'd build a new platform and base a new IdP release on that, some time after Spring Framework 6 and the other dependencies are stable, possibly end 2022 to early 2023.