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.
Big day on Tuesday! The second edition of JakartaOne Livestream happens on December 8, 2020. Make sure you are registered!
I am really looking forward to hosting this event together with Tanja. We have an amazing lineup of speakers and lots of great Jakarta EE and MicroProfile content prepared for you.
Between each session, we will return to Studio Jakarta EE for lightning talks, interviews, tech demos discussions, and awards. And, of course, there will be cake!
The Jakarta MVC 2.0 release review ballot has started. The ballot period is 14 days, so it will conclude on December 17, 2020. We are extremely happy to be able to embrace the jakarta.* namespace and run on top of Jakarta EE 9 so quickly after its release.
Eclipse GlassFish 6.0.0 is just around the corner. The release candidate (RC2) has been available for a while, and the team is working on wrapping up the last bits and pieces to release the final version. Hopefully, it will be available for download on Tuesday.
Before a Jakarta EE specification can be released under the Jakarta EE Specification Process (JESP), it has to go through a release review. The ballot for Jakarta MVC 2.0 can be followed in this ballot thread.
The release review is initiated by creating a Pull Request to the Jakarta EE Specifications repository and request a release review by sending an email to the Jakarta EE Specification Committee. See the Jakarta MVC 2.0 pull request to check out the details and follow the ballot on the public Jakarta EE Specification Committee mailing list. It took a while from the request-email until the ballot was started for Jakarta MVC 2.0, but the specification committee now has a streamlined process established for assigning a mentor responsible for starting the ballot.
I will use Jakarta MVC as an example for a specification going through the steps involved in the JESP and blog about it here. Follow the Jakarta MVC tag to get them all.
Jakarta EE 9 is out, and with it the namespace change from javax.* to jakarta.*. When we talk about the namespace change, we mostly talk about changing the import statements in your code when migrating to Jakarta EE 9. But there is more to it. I have created a slightly more advanced “Hello, World” application in order to highlight a couple more. I won’t claim that these are all areas, but I hope I have touched most…
While this may seem like slightly overkill for a “Hello, World” application, but it is also a very good example of the different areas of your codebase that are affected by the new namespace: – Maven dependencies – Import statements and fully qualified class names – XML Schema namespaces – Properties – Bootstrapping – Dynamic data
During one of the Studio Jakarta EE 15-minute sessions of JakartaOne Livestream 2020, I will convert Complete Duke from Jakarta EE 8 to Jakarta EE 9 in 15 minutes or less!
The code is available on GitHub where there is a step-by-step guide you can follow to perform the same migration as I will do live during JakartaOne Livestream 2020. This is a session you will want to attend!
On Saturday, I will present Jakarta MVC 2.0 at the Kotlin Hyderabad Community. In this talk, I will go through a bit of the history behind Jakarta MVC, as well as showing it in practice. Be prepared for an intense Live Coding session!
Jakarta MVC 2.0 is planned to be released later in December, so this talk is a preview of what’s coming.
