[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] JCP and existing specs

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