Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Java Standards Institution
Agreed. If the JCP is not able to fulfil our purposes anymore, we should replace it with something else that serves the same goal. Forking it for each project is not an option.

I'm a bit worried that this may end up being just a totally new and unofficial project, based on what Java EE once was, and independent of Java development. Or in other words, a new Spring, just more open and with broader vendor support. The little interesent shown on retaining the permission to use tha "javax" packages is a sign of this.

A new JCP might be needed for Java to evolve, in case we can't change it enough. But in the meantime, we should still use the JCP where it can help, in a similar way that MicroProfile has done with MP Config.


Regards,

Guillermo González de Agüero

El mar., 3 oct. 2017 a las 23:33, Markus KARG (<markus@xxxxxxxxxxxxxxx>) escribió:

Esteemed Java Experts,

 

I quietly followed the discussions around JCP, non-JCP, and Eclipse Foundation in this mailing list, and feel the need to chime in here.

 

There is one and only one institution which "for all times" MUST stay the one and only institution providing standards for the Java universe, and it currently is the JCP. Fullstop.

 

Why? Because, once we start to have a second institution, there soon will be a third, and a forth, and… we end up with no standards anymore. One world, one Java, one standards institution.

 

Having said that, this does not mean that that the JCP must stay as it is or be named as it is. We can change the JCP, or we can replace it by a follow-up organization inheriting everything from it. Name it "Java Foundation" for Duke's sake. But it still must be the the one and only. And we must be clear, if we want this step, this step MUST include Java SE, and it MUST include the Java trademark. Hence, it MUST include Oracle's confirmation to that. Otherwise we end up with a split community, which in the end, is not "one" community anymore, but lots of different communities -- and that will defintively be the end of Java as THE unique platform, and is to be avoided at all means.

 

Hence, knowing that it sounds like a dictator (which clearly I am not, but which helps getting back to focus), we immediately MUST stop any discussions that will point in a direction that Java standards will -even additionally- be set by anybody else than the JCP. The EE4J charter solely is to propose and lead future JSRs within the JCP, not to replace the JCP.

 

Regards

-Markus

(JSR 370)

_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community

Back to the top