Welcome to issue number one hundred and fifty-one of Hashtag Jakarta EE!
Congratulations to the Spring Team for the release of Spring Framework 6.0! This is the first major release of Spring Framework in more than five years as Spring Framework 5 was released in September 2017.
Among other things, version 6 comes with a Java™ 17+ baseline as well as support for Jakarta EE 9+. The plus (+) behind the 9 for Jakarta EE indicates that they have incorporated support for a couple of the Jakarta EE 10 specifications, such as Jakarta Servlet 6.0 and Jakarta Persistence 3.1. Make sure to check out their wiki for guidance on how to upgrade to Spring Framework 6.0.
The Jakarta EE Platform Call for the last couple of weeks has been almost entirely about TCK challenges. The Challenge part is an important part of the Jakarta EE TCK process to ensure that the specifications are 100% implementable. Even if writing tests usually aren’t seen as glorified as writing other parts of the software, this is where you really can make an impact. The efforts around refactoring the Jakarta EE Platform TCK is a massive undertaking, and we can use all help we can get. The Monthly Jakarta EE TCK call (check the Jakarta EE Specifications Calendar) is an excellent place to start if you are curious about this.
Another important update is that there will be no Monthly Jakarta EE Architecture Call in December since it conflicts with JakartaOne Livestream 2022. We also decided to skip the January call due to the Holidays, so the next Monthly Jakarta EE Architecture Call will be on February 7, 2023, at 11:00 AM Eastern Time.
The agenda for JakartaOne Livestream on December 6, 2022, has been published. Please check it out, and register so you are guaranteed to receive all relevant information as soon as it is made available!
One thought on “Hashtag Jakarta EE #151”