| 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.
-Markus
From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Leonardo Lima
Sent: Donnerstag, 30. November 2017 20:06
To: EE4J community discussions
Subject: Re: [ee4j-community] JCP and existing specs_______________________________________________
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?
Regards,
Guillermo González de Agüero
El jue., 30 nov. 2017 a las 19:46, Leonardo Lima (<leomrlima@xxxxxxxxx>) escribió:
Hello, Guillermo.
"Does it mean existing specs will need to be continued on the JCP after the Eclipse donation?"
My understanding is that this means that there might be Maintenance Releases of these JSRs fixing bugs or updating the JCP version, for example.
New versions of the Java EE / EE4J Specs would *not* be done thru the JCP.
Regards,
Leo.
On Thu, Nov 30, 2017 at 12:21 PM, Guillermo González de Agüero <z06.guillermo@xxxxxxxxx> wrote:
Hi,
Reading the JCP september minutes, I find the following statement from Will Lyons: "[...] existing Java EE specs and maintenance would continue through the JCP, but Oracle does not expect to file new JSRs for Java EE related technologies. [...]"
Everything I've read in this list indicated EE4J would have no relationship with the JCP. Does it mean existing specs will need to be continued on the JCP after the Eclipse donation?
Regards,
Guillermo González de Agüero
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
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