Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Implementations requirements

Dmitry Kornilov wrote on 06/21/2018 02:30 PM:


On 21 Jun 2018, at 22:50, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

Yes, by "platform" I meant something similar to the Java EE platform (what some people think of as the "full profile").  Not necessarily everything defined by the Jakarta EE process, but everything we think should be made available in full implementations of the platform.

If there's no interest in defining such a thing going forward (i.e., there will be no "Jakarta EE 8" or "Jakarta EE 9"), then what's the purpose of Eclipse GlassFish?

Jakarta EE (8, 9, … , n) can be only a set of APIs + TCKs. It can be released without any implementation. Implementations are released sometimes later (after the platform release) to not be a blocker of the platform release.
As I said previously, Oracle does not support a specification process that
allows this.

If you want to define "Jakarta EE 8" as "not a specification", and for which no implementation or compatibility test suite is required, then that's a different issue.  I don't know what you would call that thing, or decide whether to allow the use of the Jakarta EE brand with it.


Back to the top