Summing up Jakarta MVC 2.0

This post concludes the mini-series about how Jakarta MVC 2.0 moves through the steps involved in the Jakarta EE Specification Process (JESP).

All the posts are listed here, so bookmark this page for reference if you are involved in, or planning to be involved in a Jakarta EE specification.

Jakarta MVC 2.0 Plan Review
Jakarta MVC 2.0 Progress
Jakarta MVC 2.0 TCK
Jakarta MVC 2.0 Release Review
Jakarta MVC 2.0 Released

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.

Jakarta MVC 2.0 Released

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.

The MVC 2.0 API maven coordinates are:

<dependency>
  <groupId>jakarta.mvc</groupId>
  <artifactId>jakarta.mvc-api</artifactId>
  <version>2.0.0</version>
</dependency>

The Eclipse Krazo 2.0.0 maven coordinates are:

<dependency>
  <groupId>org.eclipse.krazo</groupId>
  <artifactId>krazo-core</artifactId>
  <version>2.0.0</version>
</dependency>

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.

Jakarta MVC 2.0 Release Review

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 MVC 2.0 TCK

A specification must, according to the Jakarta EE Specification Process (JESP), provide a test suite to verify that an implementation implements the specification correctly. This test suite is called a Test Compatibility Kit (TCK). There must be at least one compatible implementation, i.e. an implementation that passes the TCK, for a spec to be ratified as a final specification.

Eclipse Krazo 2.0.0 is a compatible implementation of Jakarta MVC 2.0. In the following video, I show how the TCK is run to verify that Krazo passes the Jakarta MVC 2.0 TCK.

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 MVC 2.0 Progress

The work with Jakarta MVC 2.0 goes forward. According to the Jakarta EE Specification Process (JESP), we are now in the development phase where we will release as many milestones as we need until we are satisfied to move on to finalize the specification.

There are already Milestone 1 releases available of both the Spec+API and the TCK in Jakarta Staging in which the namespace switch from javax.mvc.* to jakarta.mvc.* is done. The ongoing work is to update Eclipse Krazo to the new namespace and pass the TCK.

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 MVC 2.0 Plan Review

We are ready to move forward with the namespace change from javax.mvc.* to jakarta.mvc.* for Jakarta MVC. This will be released as Jakarta MVC 2.0.

According to the Jakarta EE Specification Process (JESP), we need to engage in a plan review with the Specification Committee.

The key goal of this release is to switch the namespace for the API from javax.mvc.* to jakarta.mvc.*. No additional features are included in order to make the transition from Jakarta MVC 1.1 easier.

The plan review is initiated by submitting a Pull Request to the Jakarta EE Specifications repository. See Plan Review for Jakarta MVC 2.0 to follow the progress and join the mvc-dev mailing list to participate in the release.

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.