Welcome to issue number two hundred and sixty-six of Hashtag Jakarta EE!
I am on vacation in Indonesia this week, so this post will be a tad shorter than usual.
Java is always close. Right now closer than ever for me since it is just over the horizon. Jakarta is there on the other side as well, so I make sure to wear all the appropriate Jakarta EE branded gear while walking along the beach. So far, nobody has made any comments, though…
If you never experience the need to look up the term Bali Belly, you should consider yourself lucky.
The work with Jakarta EE 11 continues, I keep an eye on the activity on the various lists and forums even when I am not actively participating. Maybe Web Profile will be releases when I come home…?
Welcome to issue number two hundred and sixty-five of Hashtag Jakarta EE!
Here’s some good news! The Jakarta NoSQL project is ready to release version 1.0 of the specification. At the moment, they are putting together the last bits and pieces of the material required for the release review by the Jakarta EE Specification Committee. You can look at it in the pull request for that purpose. It is a big milestone for a Jakarta specification project to release the first version of a specification. Congratulations to the team!
As for Jakarta EE 11, the Jakarta EE TCK project members continue their efforts to finalize the Jakarta EE Web Profile 11 TCK. There are just a couple of tests remaining and the focus is currently on updating the TCK User Guide for the refactored way of running the tests. You can follow their progress on their GitHub Project Board.
I will be on vacation for the next few weeks but don’t despair. As usual, I will monitor the progress and publish Hashtag Jakarta EE every week.
Welcome to issue number two hundred and sixty-four of Hashtag Jakarta EE!
The latest news about the refactoring of the TCK for Jakarta EE 11 is that the team is getting closer to releasing Jakarta EE Web Profile 11. There are just a small number of tests remaining to be refactored, and the rewriting of the TCK User Guide has started.
You can also join the Jakarta EE Future Directions interest group and participate in high-level discussions about how the platform should evolve. If you’re not able to join the bi-weekly calls (calendar), you can always join the mailing list and participate there as well.
Welcome to issue number two hundred and sixty-three of Hashtag Jakarta EE!
Jakarta EE Core Profile 11 was released in December. You can check out all the details on the updated Jakarta EE Core Profile 11 specification page. The next out will be Jakarta EE Web Profile 11, which will be released as soon as there is a compatible implementation that passes the refactored TCK. The Jakarta EE Platform 11 will follow after the Web Profile.
To use Jakarta EE Core Profile 11, simply add the following dependency to your application and run it with a Jakarta EE 11 Core Profile 11 compatible runtime.
January is traditionally a calm month for conferences, but also probably the busiest period for call-for-papers. Most of the conferences coming up in the next 6-9 months have CPPs open now. Make sure to check out my Jakarta EE Developer Advocate page to check out my upcoming speaking engagements.
Even this year, we will have a track at Devnexus entirely dedicated to Jakarta EE content. Check out the talks, and go ahead with your registration. You don’t want to miss out on Devnexus! This year will be even more special with the celebration of Java’s 30th anniversary.
Welcome to issue number two hundred and sixty-two of Hashtag Jakarta EE!
HAPPY NEW YEAR!
The first Hashtag Jakarta EE of 2025, with more to come. I hope you enjoy these weekly updates of what’s happening in the community in general, and Jakarta EE in particular. Most of us are getting back to work next week, so there will be more to report in next week’s edition.
Getting the final pieces of the Jakarta EE 11 release wrapped up and shipped will be our main focus at the beginning of the year. But we will also start looking ahead and get started with the planning for Jakarta EE 12. We have created an EE12 label in the Jakarta EE Platform GitHub Issue tracker for features and improvements being discussed for Jakarta EE 12.
Welcome to issue number two hundred and sixty-one of Hashtag Jakarta EE!
I hope you’re all enjoying some weeks off work. I certainly am! It’s been a while since I had this much time at home. In fact, I have two months of not traveling for work at all.
Since Jakarta EE hasn’t had much going on these weeks, this post is pretty short. Hopefully, you are all too busy doing nothing to even notice it.
I hope most of you are having some time off work now, and most likely have better things to do than reading my ramblings on a Sunday at the end of December.
We did release Jakarta EE Core Profile 11 in 2024, so I guess we can celebrate that we partly met the goal of making Jakarta EE 11 available this year. The final release of the Platform and Web Profile specifications will have to wait until 2025 to be published. On the bright side, all the individual component specifications have been available since before summer. They were actually all released as early as in May.
Even if Jakarta EE 11 is not fully out of the door yet, we have stared the planning toward Jakarta EE 12. Join the Jakarta EE Platform calls (Tuesdays at 11:00 AM EST) to join the dicussons.
This may seem like a small thing, but it is actually a major milestone for the Jakarta EE Platform Project. It is the first time we have released on of the profiles independently. This is something we probably will see more often going forward. The Jakarta EE 11 Platform and Jakarta EE 11 Web Profile will most likely not be released this year, as we were hoping. The Jakarta EE TCK project is now focusing on finishing up the refactoring of the tests for Jakarta EE Web Profile first before the Jakarta EE Platform. This will potentially enable Web Profile to be released independently prior to the Platform as well.
I had a short trip to Warsaw for Ya!vaConf last week. This was my last conference of the year. I will publish a writeup that summarizes the conference year of 2024 shortly. While waiting for that, you can check out the list on my Jakarta EE Developer Advocate page. You will also find the list of the confirmed upcoming events in 2025.
Welcome to issue number two hundred and fifty-eight of Hashtag Jakarta EE!
The ballot for Jakarta EE 11 Core Profile is complete! This means that the specification is ratified and can be released. This is a milestone on several levels. First, we released (at least part of) Jakarta EE 11 in 2024. Second, we released the Core Profile specification independently of the Platform and Web Profile specifications. This is something we have wanted to do for a while and is a verification that we have been able to untangle the dependencies enough to make it possible.
Last week, we hosted the sixth edition of JakartaOne Livestream. My short blog post about it includes the teaser for this year’s keynote video. We had great fun creating the video as you can see from the ending of it here. You can see the full version on the Jakarta EE channel on YouTube shortly.
My last speaker appearance for the year will be at Ya!vaConf in Warsaw next week. You can register with a 20% discount using the code YAVA24SP20. This will be my first time speaking at this conference. I look forward to seeing you there!
Welcome to issue number two hundred and fifty-seven of Hashtag Jakarta EE!
My last conference of November was Porto Tech Hub 2024. It has been a busy couple of months, and it isn’t over just yet. There are two conferences on my agenda in December. First up is the sixth annual JakartaOne Livestream. The week after, I will speak at Ya!vaConf 2024 in Warsaw.
Jakarta EE Core Profile 11 is about to be released. The release review is ongoing, and there are enough votes to reach the required super-majority. The ballot will close as soon as all members of the Specification Committee have voted, or at the latest on December 4, 2024.
It does not look that good for the Jakarta EE Platform and Web Profile. The platform project is exploring every option for how to be able to get the TCK in such a state that a compatible implementation could pass it, thus being able to initiate the ballot for release review by the end of the year.