5 minutes with the PMC Lead of EE4J
What is Jakarta EE? What does it mean for a project to go open source like Java EE? In this interview, Ivar Grimstad, the PMC Lead of EE4J, gave us five minutes of his time to tell us about EE4J and Jakarta EE.
We asked the Project Management Committee Lead of the EE4J, Ivar Grimstad, to answer a few questions about EE4J and Jakarta EE. We hope this short interview provides you with a quick insight into the motivation behind EE4J and Jakarta EE before reading the rest of the articles in this month’s newsletter.
Eclipse Foundation: What is EE4J?
Ivar Grimstad: Eclipse Enterprise for Java (EE4J) is the top-level project at the Eclipse Foundation for all the projects that will form the base for Jakarta EE. The EE4J projects are a mix of API projects and open source implementations of those APIs. It also contains projects for the TCKs (Technology Compatibility Kit).
Eclipse Foundation: What is Jakarta EE?
Ivar Grimstad: Jakarta EE is the name of the platform governed by the Jakarta EE Working Group. The first version will be Jakarta EE 8 which will be based on the Java EE 8 technologies transferred from Oracle to the Eclipse Foundation.
Eclipse Foundation: What is the difference between EE4J and Jakarta EE? Are there two top-level projects?
Ivar Grimstad: Jakarta EE is the brand name for the platform, not a top-level project. It is based on technologies produced by the EE4J projects. The Jakarta EE platform may also include projects outside of EE4J.
Eclipse Foundation: What is the role of the PMC?
Ivar Grimstad: The EE4J Project Management Committee (PMC) is responsible for maintaining the overall vision for the top level project. It will set the standards and requirements for releases and help the projects communicate and cooperate.
Eclipse Foundation: What does it mean for Java EE to move from proprietary to open?
Ivar Grimstad: I am not sure I agree with characterizing Java EE as proprietary. Java EE has been a community-driven standard for enterprise software developed through the Java Community Process (JCP). Contributions have come from commercial organizations, individuals, and non-profit organizations. The main difference going forward will be in the licensing and flow of intellectual property. Rather than having Expert Groups and Specification Leads, as we are used to from the JCP, the projects will be run as traditional open source projects. This means that there will not be a single specification lead (Company) that owns the intellectual property.
Eclipse Foundation: How do you see Java EE evolving at the Eclipse Foundation as Jakarta EE?
Ivar Grimstad: I expect to see Jakarta EE evolve faster at the Eclipse Foundation with more frequent releases and shorter time-to-market for newer technologies and innovation to enable standardized, portable, cloud-native Java applications.
Eclipse Foundation: How do you feel about the move of Java EE teachnologies to the Eclipse Foundation?
Ivar Grimstad: The massive amount of traffic on the mailing lists shows how engaged this community is. It just continues to amaze me how many individuals and companies that are so eager to contribute that they can barely wait. The folks at Oracle and the Eclipse Foundation are doing an excellent job of getting the transfer done and bootstrapping all the projects.
This post was originally published in the May 2018 issue of the Eclipse Newsletter: A First Look at Jakarta EE
For more information and articles check out the Eclipse Newsletter.