Welcome to issue number two hundred and eighty-three of Hashtag Jakarta EE!

The long-awaited release of Jakarta EE 11 Platform is imminent. The pull request with the material for the release review has been created by the Jakarta EE Platform project. Eclipse GlassFish passes the TCK on both Java SE 17 and 21, so as soon as the results have been summarised and the Compatibility Certification Request created, the release review ballot can open.

As i mentioned last week in Hashtag Jakarta EE #282, all plans for the Jakarta EE 12 specifications have been approved. The next step for the Jakarta EE Platform project is to define a Milestone 0. This milestone will contain certain steps that are expected of the various specification projects to complete. These steps may include verification of CI Jobs and configuration to be able to publish to Maven Central after the end-of-life of OSSRH, and more.

My next conference is coming up on June 7. I will give a presentation about the past, present, and future of enterprise Java at JJUG CCC 2025 Spring in Tokyo. I spoke at their fall-edition in November, and I am looking very much forward to going back to the vibrant city of Tokyo.,

Welcome to issue number two hundred and eighty-two of Hashtag Jakarta EE!

I have just returned from Spring I/O 2025 in Barcelona. A write-up from this conference will follow shortly. This was my last conference in May, so I have a couple of weeks break before the next one, which will be JJUG CCC 2025 Spring in Tokyo.

From what I can see on the Jakarta EE TCK Slack channel, the Jakarta EE 11 TCK is very close to being finalized, so it looks like we are on the path of getting the Jakarta EE 11 Platform release out the door in the middle of June.

The work with Jakarta EE 12 is on track according to the Jakarta EE 12 Release Plan. Plan reviews have been completed, and discussions right now are around which specifications to add (if any) to the Platform, and which to possibly deprecate. This is the time to join the weekly Jakarta EE Platform calls if you want to be a part of influencing the direction of Jakarta EE!

Welcome to issue number two hundred and eighty-one of Hashtag Jakarta EE!

This week, I a was in Cologne for JCON Europe 2025 where we among other things celebrated 30 Years of Java. Check out my write-up from the event to learn more. Next week, I will be going to Barcelona for Spring I/O. It will be my second time speaking at this event. I expect that it will be just as awesome this year as it was a year ago.

The release of the Jakarta EE 11 Platform specification is right around the corner. The issues with the serivce outage that affected our Jenkins CI instances are now resolved, and the work is progressing. The release date is expected to be in June.

All the plans for Jakarta EE 12 have been completed and approved (with the exception of Jakarta Activation, which will have its plan review started on Monday).

Two interesting specifications that are now being moved over to the jakarta.* namespace are Jakarta Portlet and Jakarta Portlet Bridge. While the concept of portlets may at first thought feel like a blast from the past, it can also be seen as the revival of a stable, well-tested, robust way of creating Micro Frontends. Micro Frontends are defined as “An architectural style where independently deliverable frontend applications are composed into a greater whole”, and Jakarta Portlet enables the development of modular, reusable web components called portlets, hence reusable Micro Frontends.

Welcome to issue number two hundred and eighty of Hashtag Jakarta EE!

This Monday I hosted Javaforum Malmö where we got an interesting presentation by Artur Skowroński about AI in the context of the JVM as he was passing by Malmö on his way to Devoxx UK. If you are a speaker passing by Malmö, or interested in trying out as a speaker, please do contact me so we can make it happen.

The service outage set us back a couple of weeks regarding the Jakarta EE 11 release, but the CI instances are now recovered (at least the one’s we are dependent on for this release), so the work can go on. The TCK project seemed optimistic on the call this Wednesday, so it looks like we are on track to get the release out the door by June.

I will be at JCON 2025 in Cologne, Germany the upcoming week. Together with Rustam, I will present Duke on CRac with Jakarta EE. I will also hang around the Eclipse Foundation booth together with Tanja.

On Wednesday morning, you can join me for the traditional #runWithJakartaEE morning run at JCON. We will meet at 6:30 AM outside the venue (Cinedome Multiplex Cinema) and go for a refreshing 5K run in a park nearby.

Welcome to issue number two hundred and seventy-nine of Hashtag Jakarta EE!

The service outage is more than just your regular neighborhood outage. It seems to be a massive breakdown of a storage cluster that is a central piece on which all the Jenkins CI instances depend. The Jakarta EE TCK project has asked for a restoration from an old backup to continue the work on finalizing the Jakarta EE 11 TCK. We are crossing our fingers that this will be available soon.

Luckily, the outage does not affect the Jakarta EE 12 Plan Reviews, so they go according to plan. Check out the status board for the current status.

My next conference will be JCON Europe in Cologne on May 12-15. The talk I will have there is with Rustam about how to use CRaC (Coordinated Restore at Checkpoint) with Jakarta EE. Make sure to come to this session for a fun introduction to CRaC and Jakarta EE.

Besides this session, you can also meet me at the Eclipse Foundation booth in the exhibition area. Tanja and I will staff the booth together with some of our most eager community members.

Welcome to issue number two hundred and seventy-eight of Hashtag Jakarta EE!

Last week, I was in Bangalore speaking at GIDS. Read all about it in my write-up from the event. I now have a couple of weeks at home before my conferences in May, which will be JCON Europe, followed by Spring I/O.

The work on finalizing the TCK for Jakarta EE 11 Platform progresses. There was a major service disruption of the Eclipse Foundation services last week that affected all the CI services. This is obviously not optimal for work with the TCK since the use of Jenkins CI is fairly extensive to be able to run all the tests. Hopefully, the services can be up again soon, so it does not affect the plan of releasing the Jakarta EE 11 Platform in June.

The plan reviews for the Jakarta EE 12 specifications are moving along. Check out the progress in the Jakarta EE 12 Plan Review status board. As soon as the component specifications have started their plan review, it is expected that the plan review for Jakarta EE 12 Platform, Web Profile, and Core Profile specifications will start.

In addition to the specifications targeting Jakarta EE 12, we also have two creation reviews coming up for Jakarta Portlet and Jakarta Faces Bridge. These specifications have so far been maintained under the JCP, and they have now decided to move them over to Jakarta EE and the jakarta.* namespace.