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.
— Dmitry
Richard Monson-Haefel wrote on
06/21/2018 07:08 AM:
If, by platform, you mean the full Java/Jakarta EE
stack than I would say, no. I would prefer that if there is a
"platform" that it represents the entire Jakarta EE ecosystem,
for which there is no implementation, or that it be confined to
a very small set of "core" technologies. Either way, the set of
reference implementations that have been donated by Oracle (e.g.
Eclipse, etc.) should be separated as a top-level project from
the Jakarta EE Specification Working Group.
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________ jakarta.ee-spec.committee mailing list jakarta.ee-spec.committee@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|