|Re: [ee4j-community] JCP and existing specs|
Reza, to be absolutely clear: *Whether or not* a standardization will actually happen, and whether the EE4J PMC will *actually* serve as JSR spec leads, is not yet decided by the PMC. What I wrote the is just the de-facto status in case a Java Standard has to be done *now*. Nobody right now wants such a standard, so this is a purely theoretical analysis of the current legal state. This may and possibly will change in (near) future, and is mostly up to the trademark holders and the free will of the PMC. Also, it cleary looks like there will never be a "Java EE" outside of Oracle's ownership, not today and not in future, as they do not (yet) intend to give away that trademark to the Eclipse Foundation. "EE4J != Java EE"; EE4J v1 will be an implementation of Java EE 8, but EE4J v2 might be something different, and (while being higly unlikely) at least in legal theory there could be a Java EE 9 published by Oracle but not being covered by EE4J. One is a trademark (purely legal issue), the ther is a development project (IP on source code). The PMC decides about "EE4J". Oracle decides about "Java EE". Just to be absolutely clear.
I sure do hope what you say is true at this point. While it would have been really great to decouple Java EE from the Oracle realm of ownership, perhaps the JCP is the best bet in getting branding and packaging issues with the EE4J move resolved.
Even with the JCP, Oracle will still not allow a non-Oracle JSR to use the Java name, but at least the javax package would be secured without a bitter struggle.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Markus KARG <markus@xxxxxxxxxxxxxxx>
Date: 12/1/17 3:08 AM (GMT-05:00)
To: 'EE4J community discussions' <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] JCP and existing specs
There is a very good reason to do so. IMHO the JCP is -still- the sole standardization organization which is allowed to publish official industrial standards bearing the word "Java" in the standard's name. Oracle has not yet officially announced its will to change that. Eclipse is just the place where we all work together to develop the content of these specs (spec text, APIs, RIs, TCKs), but at the end, it is -still- up to the JCP to accept it as an official standard. Hence the Eclipse projects will do "code first" approach and ask the JCP for official standardization afterwards. This "separation of concerns" also is what the EE4J PMC and Mike Milinkovic told me at EclipseCon Europe 2018, and I doubt it has changed since. So the EE4J PMC simply serves as the new spec lead in the JSRs, and fulfils all duties like organizing the expert groups (= the EE4J Subprojects) and filing the needed paperwork.
I'd say "none"? :)
On Thu, Nov 30, 2017 at 12:58 PM, Guillermo GonzÃlez de AgÃero <z06.guillermo@xxxxxxxxx> wrote:
Maintenance releases are not allowed until everything has been moved to Eclipse (at least that's what we were told these days when asking for a Security API MR). At that point, and if we finally decide to move away the JCP, what would be the reason to do MRs there?
Guillermo GonzÃlez de AgÃero
El jue., 30 nov. 2017 a las 19:46, Leonardo Lima (<leomrlima@xxxxxxxxx>) escribiÃ: