MVC 1.0 JSR will soon belong to the community
Oracle announced in the Java EE community survey results that, in addition to withdrawing the JSRs for Management 2.0 (JSR 373), and JMS 2.1 (JSR 368), they are also “investigating a possible transfer of MVC to another community member or organization in order to complete JSR 371 as a stand-alone component.” Now it seems that its fate will be sealed on January 31.
Oracle conducted a survey in September-October 2016 regarding future enhancements to Java EE in the context of the revised roadmap presented at JavaOne 2016 and presented the results in late December.
They revealed that Management, JMS, and MVC ranked low in survey results (the ranking supports their proposal to withdraw new APIs in these areas from Java EE 8).
We have withdrawn the JSRs for Management 2.0 (JSR 373), and JMS 2.1 (JSR 368), and are investigating a possible transfer of MVC to another community member or organization in order to complete JSR 371 as a stand-alone component.
Now it seems that the fate of MVC will be sealed later this month. Santiago Pericas-Geertsen and Manfred Riem, MVC spec leads, announced that they have initiated a Transfer Ballot as per JCP 2.10 and proposed to transfer the MVC 1.0 JSR from Oracle to Ivar Grimstad. They also revealed that the EC will be voting on it and the ballot will close January 31st.
If it is accepted Ivar will become your new sole spec lead.
— Java EE Platform (@Java_EE) January 17, 2017
Oracle has tranferred ownership of the MVC JSR to the community! Now you can help make it a community sucess story! https://t.co/IeHpViObxG
— Java EE Guardians (@javaee_guardian) January 18, 2017
News travel fast: MVC to be transferred to the community
Long-time consultant Reza Rahman shared the news with the community and urged people to “contribute to the MVC specification now more than ever. It is very important that together we demonstrate that the community alone can make Java EE ecosystem JSRs successful even without Oracle or any other major vendor.”