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.

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

It has been quiet around Jakarta MVC for a while, so I am happy to announce that Jakarta MVC 3.0 is under release review as we speak. This release is aligned with Jakarta EE 11 Web Profile and comes with the following features:

• CSRF projection by default
• Accessor for form method to overwrite the field name
• Replace the proprietary Krazo default view extension with an API constant
• Remove the requirement for implementations to support the Facelets view engine

Eclipse Krazo 4.0.0 comes in two flavours: Eclipse Krazo for Jersey and Eclipse Krazo for RESTEasy. Eclipse Krazo for Jersey 4.0.0 passes all the Jakarta MVC 3.0 TCK tests, while Eclipse Krazo for RESTEasy 4.0.0 has one test failing at the time of writing this post.

A plan for Jakarta MVC 3.1 is also proposed and currently being reviewed. This release will align with the proposed Jakarta EE 12 APIs. Maybe this is the release MVC will make it into Jakarta EE Web Profile? Which brings us over to Jakarta EE 12. The plan reviews for the specifications targeting Jakarta EE 12 are going on. The Jakarta EE 12 Plan Review Status board shows the current status of these plan reviews.

Coming up this week for me is GIDS in Bangalore, India. This year, I have two talks scheduled: Jakarta EE Meets AI and Boost Your Performance and Developer Productivity with Jakarta EE 11. On Tuesday night, I will participate in the BevRelJam Bengaluru – April 2025 together with a couple of the other speakers at GIDS. I look forward to engaging with the Indian Developer Community this week.

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

We are getting closer and closer to finalizing the refactoring of the Jakarta EE Platform TCK. The goal right now is to have the Jakarta EE 11 Platform ready for release review by the end of May 2025. Stay tuned for updates.

Plan reviews for Jakarta EE 12 are going on as we speak. Check out the progress in the Jakarta EE 12 Plan Review status board. My guess is that we will see quite a few more coming forward as the April 15 deadline is fast approaching.

The 2025 Jakarta EE Developer Survey is ongoing. If you haven’t done it yet, please respond to help us shape the evolution of Jakarta EE. It is important for us to gather the perspective from a diverse audience, so we have made the survey available in multiple languages, including  English, Spanish, Portuguese, Japanese, and Chinese.

Participate Today!

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

Jakarta EE 11 Web Profile is released! It’s a little later than planned, but we’re finally there, and Jakarta EE 11 Web Profile joins Jakarta EE 11 Core Profile among the released specifications. It has been a tremendous effort to refactor the TCK.

Eclipse GlassFish was used as the ratifying compatible implementation of Jakarta EE 11 Web Profile. It would expect other implementations, such as Open Liberty, WildFly, Payara, and more to follow suit over the next weeks and months. Check out the expanding list of Compatible Products of Jakarta EE 11.

JavaLand 2025 happened last week. You can read about it in my blog post from the event. I will now be at home for the next couple of weeks before traveling to Bangalore, India for the Great International Developer Summit (GIDS).

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

The Release Review for Jakarta EE 11 Web Profile has started! According to the process, it will conclude on April 7 at the latest. When I write this, seven out of ten members have voted +1, which means that super-majority is reached and Jakarta EE 11 Web Profile in practice has passed the release review.

So, what about the Jakarta EE 11 Platform? The status, as of Wednesday is that we are down to ~50 test failures, most of which pass for Jakarta EE 11 Web Profile. This is an indication that there is some configuration or setting for the CI jobs that may be the problem.

Plan reviews for the component specifications targeting Jakarta EE 12 are ongoing. So far eight specifications have completed, or are in the process of completing their plan reviews. More are expected to follow as we get closer to April 15, the deadline communicated by the Jakarta EE Platform project. Check out the Jakarta EE 12 Plan Reviews Project Board for a complete overview.

In the upcoming week, I will be at JavaLand where I have several talks in addition to helping out with the booth Jakarta EE is having in cooperation with Eclipse IDE and Adoptium. I hope to see you there!

And, of course, there will be the traditional JavaLand Jogging on Wednesday morning.

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

I’m on my way home after JavaOne 2025. As usual, I will cover the conference in a separate post shortly. There was so much going on during this hectic week, so I haven’t had time to sit down and write the post yet. It was an awesome conference! If you weren’t able to attend this year, I would recommend that you do so next year.

The release review ballot for Jakarta EE 11 Web Profile is as good as ready to start. There are only some minor adjustment left until it is ready. Eclipse GlassFish has passed the TCK and the Compatibility Certification Request has been approved. Congratulations to the project for achieving this!

Another thing that surfaced seemingly out of nowhere this week was that the MicroProfile steering committee started discussing the possibility of merging MicroProfile in under the Jakarta EE working group. This is certainly a welcoming initiative as it will reduce the unnecessary confusion of these two working groups and brands. In my opinion it is a win-win for both, and something that should have happened a long time ago. The specifications will be put alongside the existing Jakarta EE specifications and making the platform more complete and offered to a broader audience by taking advantage of the stronger brand that Jakarta EE is.