![]() Instead of killing it off, they gave it to somebody in the community, Ivar Grimstad. The big changes were, they didn't want to commit to delivering the action-oriented web framework anymore. ![]() Ultimately, what Oracle committed to delivering was fairly close to what they committed in the very beginning in terms of scope. So after quite a bit of noise in the community and industry, Oracle kindly said, 'Sorry we weren't working on Java EE 8, but now we are, and we are re-committed to doing this.' They ran yet another survey, like the same survey that was done at the very beginning, to ostensibly determine whether the features we were working on in the beginning still makes sense. ![]() Together, we were basically asking questions on behalf of the community, asking why this is happening, and why no one was answering. I wound up leaving Oracle and shortly after, this "order of mission" popped up, called the Java EE Guardians. I was at Oracle at the time when this was occurring. Even in the darkest days of Sun, there wasn't a six-month hiatus where there was no visible work in the advancement of Java EE. The folks in the community noticed that after a certain period of time, in particular after JavaOne 2016, suddenly all activity on these Java EE APIs stopped for six months or more - this is unheard of. Rahman also discussed the stagnation of Java EE, the emergence of the Java EE Guardians, and the events that lead to where Java EE is today. Eclipse has created the ee4j-community mailing list and developers are encouraged to provide feedback and to contribute.Īt a recent Java Users Group meeting, well-known Java EE evangelist, Reza Rahman, presented " Java EE 8 and Java EE 9: What You Need to Know." He outlined the past, present, and future of Java EE, reviewed notable JSRs within Java EE 8, and what's on the horizon. Milinkovich also noted it will take time to get all this accomplished and interaction with the Java community still needs to be defined. Establish a new specification process under the auspices of the Eclipse Foundation.Create an open build infrastructure so EE4J can be built and tested by the community.Move the Java EE TCKs and make them available to the community.Move existing GlassFish open source projects (130 GitHub repositories). ![]() Milinkovich noted some of the significant tasks with this project: We look forward to engaging with the millions of developers and organizations using Java EE. It is a significant opportunity to use the Eclipse open development model to accelerate innovation in Java for enterprise and cloud native computing. Moving Java EE to the Eclipse Foundation is going to be an exciting and massive undertaking. Mike Milinkovich, executive director at Eclipse, formally introduced EE4J and described the challenges they face: The Eclipse Foundation is ready to take on the challenge of open sourcing Java EE as the Eclipse Enterprise for Java (EE4J) project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |