What’s going on with Jersey

Jersey is on a journey to the Eclipse Foundation. There are some consequences, unfortunately, the visible activity around the project is not great. The number of open issues is growing. New pull requests are not accepted. All because of the work being done on the donation.

But we are getting to the final. Jersey 2.27 is going to be released soon, it is legally approved for the transition to the Foundation which happens next, and then hurray! Long live Eclipse Jersey!

The Jersey code is going to be pushed to EE4J repository. The issues and PRs are going to be migrated, too. The commit history, branches, and tags are of course not donated (imagine the legal code validation needed for every commit, every tag and branch – it would take a lifetime to process through). Those will remain in current GitHub repository – which will be for reading only – any new commits and issues should go to the new Eclipse Jersey repository.

Eclipse Jersey needs to pass through legal CQ process, build infrastructure (CI/CD) needs to be set up, and that’s it, work can get started!

Posted in Jersey | 1 Comment

What’s going on with Java EE?

As it has been announced, Oracle decided to open up Java EE and donate each Java EE technology owned, to the Eclipse Foundation. This comes in four stages, and current status is reported for instance by Java Evangelist. The umbrella of once Java EE projects in the Foundation has a code name Eclipse Enterprise for Java (EE4J) and Java EE is called Jakarta EE now. There is an EE4J Project Management Committee (PMC) that sets the future development course of Jakarta EE.

This does not mean Oracle stops working on the technologies immediately after the donation. On contrary, more activity around the projects is expected, and the community would be more involved in bringing up new ideas and features. The donation, however, comes with a side effect. Every Java EE project needs to go through the code evaluation by legal. Every piece of code, as well as each dependency, needs to be verified whether the license allows it to be donated. This is a lengthy process, the bigger the project, the longer the evaluation. This process means that every Java EE project needs to be frozen, no new features can be accepted, no pull requests (PR) are merged, since each new piece of code would need to be legally processed and the donation would get longer and longer. A similar legal process is on the donor side, as well as on the Foundation side, taking even a little bit more time. Unfortunately, someone feels that’s wrong. That the project is abandoned. That no one is responding. Apologies, here are the reasons.

So does that mean the pull requests can be accepted as soon as the Java EE project is donated? Well, for each donated project, the plan is to create one last release. The same code base should be used for a very first release within the Foundation. So after the last Java EE project is donated (including the big guys Glassfish and CTS), the first release takes place. No new features, no new code, only critical fixes allowed. The PRs are merged into another branch waiting for the second release. That eventually will be the proper Jakarta EE!

Posted in Jakarta EE | Leave a comment