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

I have just arrived back home from JConf Dominica 2024, and have a couple of hours to pack my bags before heading out again for JCrete 2024. Busy times for a developer advocate, but so incredibly great to be able to connect with the Java communities all over the world.

(I don’t know if it was pure luck, or if the stars were aligned just right for me this time, but as it turned out, the only two days I was on the ground this week were the two days with Blue Screen of Death for the airlines.)

The first release candidate of Jakarta EE 11 will be published shortly. There are a couple of the specifications that have released service releases of their API artifacts, so we will gather these and release an RC1 of the Jakarta EE 11 APIs.

All the Jakarta EE 11 XML Schemas are publicly available at https://jakarta.ee/schemas/. Please check them out and let us know if you find something that needs to be corrected before the release is Final.

Another way of providing input, AND possibly winning a FREE T-shirt is to complete the 2024 Cloud Native Java Technical Survey.

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

After a couple of weeks at home, I am going on the road again. First off is JConfDomincana, the Caribbean Java Technologies Conference organized by the Dominican Republic Java User Group, where I will host a workshop together with Eudris. The topic of the workshop is creating RESTful Web Services with Jakarta EE.

As mentioned in last week’s Hashtag Jakarta EE, the refactoring of the Jakarta EE TCK is what we are waiting for to be able to release Jakarta EE 11. The TCK project has now set up a Jakarta EE 11 TCK Release GitHub Board where we can follow the progress of this work.

I also mentioned that the Jakarta EE Platform project has started planning for Jakarta EE 12. To facilitate this planning, we would really like to have YOUR which you can provide by completing the 2024 Cloud Native Java Technical Survey. Note that this survey is different from the Jakarta EE Developer Survey we conducted earlier this year.

The program for Open Community for Java will be published in the upcoming week. Meanwhile, you can check out the featured speakers and why not just register while you’re at it? The conference is in Mainz, Germany October 22-24.

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

Last week I was speaking at Developer Week’24 in Nuremberg, Germany. That was my last conference of the European conference season before summer. This year, there will be a couple of conferences during the summer before the fall season start up. In a couple of weeks, I will host a workshop at JConfDominica 2024 before going directly to Greece for JCrete 2024.

Jakarta EE 11 is almost ready. All the individual specifications are done, and the Jakarta EE Platform project is finalizing the Jakarta EE Platform, Web Profile, and Core Profile specifications. The last piece of the puzzle is the work with the Jakarta EE TCK which is being refactored from Apache Ant and JavaTest Harness to a more modern approach using Apache Maven, JUnit 5, and Arquillian.

In parallel to this work, the platform project has started the discussions for a Jakarta EE 12 release sometime in the first half of 2026 with a baseline of Java 21 and verified with compatible implementations passing the TCK on Java 21 and Java 25. Note that these are very preliminary discussions and subject to change.

The program for Open Community for Java that will take place in Mainz from October 22 to 24 this year will soon be available. Take a look at the early-bird selection of speakers while waiting for the rest of the program to be published. From what I hear, the notifications to accepted speakers will be sent out this week.

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

As I wrote last week, all the Jakarta EE 11 specifications are now finished and the remaining work to get Jakarta EE 11 released is to finalize the refactoring of the TCK and have at least one open-source compatible implementation passing it.

Milestone 4 of the Jakarta EE 11 APIs are now available in Maven Central. Use these coordinates in your pom.xml to try out this version.

<dependency>
    <groupId>jakarta.platform</groupId>
    <artifactId>jakarta.jakartaee-api</artifactId>
    <version>11.0.0-M4</version>
    <scope>provided</scope>
</dependency>

I will go to Nürnberg to speak at Developer Week ’24 this week. It will be my fourth time speaking at this conference, including one online appearance during the pandemic. It does not usually gather the biggest Java crowd, but it feels like the number is increasing for each year. The conference is well-run and a very pleasant experience.

Talking about conferences, the registration for Open Community for Java is now open. If you know you are going, or usually used to attend EclipseCon, you may as well register now. The program is being finalized as we speak and you will be able to check out the speakers and their talks very soon.

Register for Open Community for Java today!

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

All the specifications that will be part of Jakarta EE 11 have passed their release review and have been, or are in the process of being released. The efforts are now on finalizing the TCK and wrapping up the changes needed in the Jakarta EE Platform, Web Profile, and Core Profile specifications.

– Jakarta Annotations 3.0
– Jakarta Authentication 3.1
– Jakarta Authorization 3.0
– Jakarta Concurrency 3.1
– Jakarta Contexts and Dependency Injection 4.1
– Jakarta Data 1.0
– Jakarta Expression Language 6.0
– Jakarta Faces 4.1
– Jakarta Interceptors 2.2
– Jakarta Pages 4.0
– Jakarta Persistence 3.2
– Jakarta RESTful Web Services 4.0
– Jakarta Security 4.0
– Jakarta Servlet 6.1
– Jakarta Validation 3.1
– Jakarta WebSocket 2.2

Now that all the specifications for Jakarta EE 11 are done, the specification projects are starting to look ahead to Jakarta EE 12 and how to further evolve the specifications. It is great to see the individual projects taking the initiative this way.

This week was dedicated to the Eclipse Foundation All Hands 2024. In the upcoming week, I will be at home before I go to Nürnberg to speak at Developer Week in the first week of July.

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

This week I was speaking at DevBCN 2024 in Barcelona. My next conference appearance will be at Developer Week ’24, which takes place in Nürnberg on July 1-5. But even if conference season is winding down for summer, I will still be found at airports here and there. Right now, I am on my way to Montreal for the early Eclipse Foundation All-Hands where I will get to meet and socialize with my colleagues from all over the World.

All the individual specifications that are targeting Jakarta EE 11 are now done. Two are still under release review with the Jakarta EE Specification Committee and will conclude at the latest on June 26. The work with wrapping up the Platform, Web Profile, and Core Profile specifications will continue along with the implementation of compatible implementation(s) for ratification as well as the refactoring efforts of the Jakarta EE TCK.

Done:
– Jakarta Annotations 3.0
– Jakarta Authorization 3.0
– Jakarta Concurrency 3.1
– Jakarta Contexts and Dependency Injection 4.1
– Jakarta Data 1.0
– Jakarta Expression Language 6.0
– Jakarta Faces 4.1
– Jakarta Interceptors 2.2
– Jakarta Pages 4.0
– Jakarta Persistence 3.2
– Jakarta RESTful Web Services 4.0
– Jakarta Servlet 6.1
– Jakarta Validation 3.1
– Jakarta WebSocket 2.2

In progress:
– Jakarta Authentication 3.1
– Jakarta Security 4.0

Milestone 3 of the Jakarta EE 11 APIs was published to Maven Central earlier this week. Please check them out and don’t hesitate to let us know if you find something that should be fixed before the final release.

<dependency>
    <groupId>jakarta.platform</groupId>
    <artifactId>jakarta.jakartaee-api</artifactId>
    <version>11.0.0-M3</version>
    <scope>provided</scope>
</dependency>