We are two weeks into the new year already, and I want to remind the specification teams that about the deadline for submitting a plan review in order to be a candidate for inclusion in the Jakarta EE 9.1 release. The deadline is January 31 as the timeline below shows.
The Jakarta EE Platform team are having weekly calls where various topics related to the platform specification are discussed. Please, do join this call if you are interested in participating in shaping the platform. Details for how to join can be found in the Jakarta EE Platform Calendar.
Barcelona JUG is the next stop on our Jakarta EE Virtual Tour. Join here! We really enjoy giving these talks, so please reach out if you are interested in hosting us at your JUG or MeetUp.
The first Jakarta EE Update Call of 2021 will happen on January 21! The topics we will cover in this call are the program plan and budget, the release plan for Jakarta EE 9.1 as well as upcoming events, programs and marketing campaigns. And, of course, there will be an opportunity to get your questions asked and answered.
Visit the Community Calendar to find the details about how to join the call.
The main goal of Jakarta EE 9.1 is to support the Java SE 11 runtime. The APIs will still be compiled to Java SE 8 level in order to be usable to both Java SE 8 and Java SE 11. That means that there will not be need for any new releases for the individual specifications unless the specification teams have changes they wish to push forward. The absolute deadline for such plans to be put forward is January 31, 2021. See the timeline below.
Note that, it is up to the platform project to decide if any new versions should be included in the Jakarta EE 9.1 release even if a plan review is submitted within this deadline.
The Jakarta EE Virtual Tour continues in 2021. The ones we have planned so far are Silesia JUG (Jan 13), JUG Darmstadt (Jan 13), Barcelona JUG (Jan 20), and Chicago JUG (Feb 25). Please reach out if you are interested in hosting us at your JUG or MeetUp.
The jChampions Conference is starting next week. I will be a moderator for at least one of the sessions. Check out the schedule.
It’s 2021 and a year since I wrote the very first Hashtag Jakarta EE. I find it useful for myself to write these short recaps of what’s going on in the community, and I hope you enjoy them as well!
On the very last day of 2020, Eclipse GlassFish 6 was released! Go to glassfish.org/download to check it out. GlassFish 6 meets the compatibility requirements of Jakarta EE 9. Downloads are available for both the Platform and the Web Profile.
If you want to have a look at the other fishes in the Jakarta EE and MicroProfile space, take a look at A day of fishing with Jakarta EE and MicroProfile by Edwin Derks. In this blog post, Edwin describes the differences and similarities between GlassFish, Payara, and Piranha.
The Jakarta EE Virtual Tour continues in 2021. The ones we have planned so far are Silesia JUG (Jan 13), JUG Darmstadt (Jan 13), Barcelona JUG (Jan 20), and Chicago JUG (Feb 25). Please reach out if you are interested in hosting us at your JUG or MeetUp.
This is the last Hashtag Jakarta EE in 2020. But don’t worry, I will continue these weekly updates in 2021 as well.
This week, MicroProfile 4.0 was released! It’s been a long wait since the previous release (3.3) back in February. But now it’s here, the first release of MicroProfile following the MicroProfile Specification Process (MPSP).
This release contains updates to all specifications. See the MicroProfile Presentation for details. Note that the four Java EE 8 specifications that form the foundation of MicroProfile have been updated to the Jakarta EE 8 counterparts. This means that MicroProfile is still on the javax.* namespace. I expect that there will be a release during 2021 that will be based on Jakarta EE 9 versions of the specifications and by that support the jakarta.* namespace.
MicroProfile 4.0 will be covered in detail in the next Studio Jakarta EE LIVE as my guest on January 28th is Emily Jiang. Make sure to tune in to get all information about the 4.0 release directly from Emily.
As I mentioned in the previous Hashtag issue, I will participate in a Tech Summary Panel organized by the Barcelona JUG on December 29. In this event, we will summarize 2020 and look ahead towards 2021. It has an amazing lineup of speakers, and I am honored to be among them. You don’t want to miss this!
I have used Jakarta MVC as an example for a specification going through the steps involved in the JESP and blogged about them here. Check out the Jakarta MVC tag to get them all.
As we are ramping down to close 2020 and recharge for 2021, there are still things going on in the community. First, I would like to point you to the Studio Jakarta EE LIVE I had with Dalia this week where we talked about tooling for Jakarta EE.
We released Jakarta MVC 2.0 yesterday! This was the second release since moving to Eclipse Foundation and Jakarta EE. With this release, we have moved to the jakarta.* namespace. Eclipse Krazo, the compatible implementation runs on both GlassFish and WildFly. OpenLiberty is on its way.
Jakarta MVC 2.0 will be featured in a session called “OpenDDR and Jakarta MVC” that I am co-speaking with Werner Keil at Java2Days on December 22nd.
On December 29th, I am participating in a Tech Summary Panel organized by the Barcelona JUG. In this event, we will summarize 2020 and look ahead towards 2021. It has an amazing lineup of speakers, and I am honored to be among them. You don’t want to miss this!
Jakarta MVC 2.0 passed the release review ballot and is now ratified as a final specification according to the Jakarta EE Specification Process (JESP).
The last steps for the project team after the ballot are to release the staged artifacts to Maven Central and verify that all published information is correct. That has now been done, and I have listed information about how to obtain the artifacts below.
In addition to the core component, you will also need a dependency specific to the Jakarta EE 9 implementation you are using. See Eclipse Krazo 2.0.0 download page for more information about this.
The MVC 2.0 TCK can be downloaded from the Eclipse Download area. It can also be obtained from Maven Central.
I have used Jakarta MVC as an example for a specification going through the steps involved in the JESP and blogged about it here. Follow the Jakarta MVC tag to get them all.
In the December 15 Platform Project call, the platform team made a couple of important decisions regarding the upcoming Jakarta EE 9.1 release.
The goal of Jakarta EE 9.1 is to ship Java SE 11 support as soon as possible. That means that we want to minimize releasing new API artifacts unless necessary. Specification teams are able to make changes and do minor updates if they wish, or have to in order to support Java SE 11. In order to avoid putting these on the critical path of the release, the platform team decided to enforce a deadline for announcing these changes. The deadline for starting a plan review for potential inclusion in Jakarta EE 9.1 is set to January 31, 2021.
Any API team that wants to release a new version MUST engage in a plan review by the end of January 2021 in order to be considered for inclusion in Jakarta EE 9.1.
The plan for Jakarta EE 9.1 has not been finalized yet but will be communicated on the Jakarta EE Platform Project pages shortly. I have taken the liberty to sketch a very loose outline for the plan below.
The only date communicated so far is the deadline for engaging in a plan review for specification projects. That deadline is January 31, 2020. The actual release date (T) is not decided yet, but it is a fair assumption that the Jakarta EE 9.1 specification will go on ballot for release review about 14 days prior to this date. Any specifications that are updated for this release will have to go to ballot before this. Preferably as soon as possible, but no later than 14 days before the platform ballot starts in order to complete on time.
A plan review is an important step in the Jakarta EE Specification Process (JESP). This is where a project team presents its plans for the Specification Team and the community for feedback.
A plan review is initiated by creating a Pull Request to the specifications repository. To make it easier for a project team to know what information to include in a plan review, the specification committee has created an example of such a pull request. The example PR contains a checklist for the project team:
## Specification PR template
When creating a specification project plan review, create PRs with the content defined as follows.
Include the following in the PR:
- [ ] A directory in the form wombat/x.y where x.y is the release major.minor version.
- [ ] An index page wombat/x.y/_index.md following [template](https://github.com/jakartaee/specification-committee/blob/master/spec_page_template.md)
- [ ] Title should be on the form "Jakarta Wombat X.Y (under development)"
- [ ] Includes a plan for the release. Usually, a couple of statements is enough. Otherwise, a link to a document describing the release.
- [ ] Includes a detailed description of any backward incompatibility (Mark with **N/A** and check if none)
- [ ] Declares optional features if there are any (Mark with **N/A** and check if none)
- [ ] Includes minimum Java SE version
- [ ] Describe any updates or required changes including splitting out the TCK (Mark with **N/A** and check if not planned)
- [ ] Link to updated release record
The planned version’s _index.md file should look something like this:
---
title: "Jakarta Wombat 1.0 (under development)"
date: 2099-12-01
summary: "First release of Jakarta Wombat"
---
Jakarta Wombat 1.0 lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
*Minimum Java SE Version:* **17**
* [Jakarta Wombat 1.0 Release Record](https://projects.eclipse.org/projects/ee4j.wombat/releases/1.0)
Instructions for Jakarta EE Specification projects regarding reviews were communicated to project leads on the Jakarta EE Specification Project Leads mailing list in this message from the Specification Committee.
Wow, fifty hashtags so far! Tuesday was a big day for the Jakarta EE community. That was the day of JakartaOne Livestream 2020. With this event, we officially announced Jakarta EE 9, even though it has been available in Maven Central since November 20th.
If you didn’t have the opportunity to attend or want to see some of the talks again, they are all available on the Jakarta EE YouTube channel. Please visit jakarta.ee to find out more about Jakarta EE, and specifically the specifications section for all resources regarding the Jakarta EE specification.
I am also happy to be back at JavaLand 2021, where I will give a talk about Jakarta EE. It will be a hybrid event, and it looks like I will do my talk remotely. I have been a speaker at every edition of JavaLand so far and always joined the JavaLand jogging on Wednesday morning. This year, I will have to do a run in the morning from my home in order to keep the spirit going.
On Thursday, I have Dalia as a special guest in Studio Jakarta EE LIVE. We will talk about tooling support for Jakarta EE. Dalia is a Developer Advocate at JetBrains and will demo the support offered by IntelliJ IDEA for Jakarta EE in this session.
Feel free to use the comments section on YouTube to ask questions for Dalia and me. You can start right now and continue until the broadcast ends. Of course, you may even ask questions after, but the chances of getting them answered are much higher during the broadcast.
