| Re: [jakarta.ee-wg] Use of Jakarta EE in EE4J project names |
Seeing Glassfish in there, since Eclipse Jetty implements the servlet-api, does this mean the intent is to move Jetty under the EE4J umbrella in this context?On Wed, Mar 28, 2018 at 12:46 PM, Mike Milinkovich <mike.milinkovich@eclipse-foundation.org > wrote:______________________________On 2018-03-28 1:32 PM, Markus KARG wrote:
(1) Does that imply that all TCKs end up in one project, or is that what project you talk about only holding the umbrella spec's own TCK?
All of the TCKs are going to be initially contributed by Oracle in one project. What happens after that will be determined by the PMC.
(2) What is the difference between Jakarta EE projects and EE4J projects?
EE4J is the top-level project where the work on the RIs and TCKs happen. Jakarta EE is a brand.
This table from my blog helps explain it, as does this Twitter thread.
Old Name New Name Java EE Jakarta EE Glassfish Eclipse Glassfish Java Community Process (JCP) [*] Jakarta EE Working Group (Jakarta EE) Oracle development management Eclipse Enterprise for Java (EE4J)
Project Management Committee (PMC)_________________
jakarta.ee-wg mailing list
jakarta.ee-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-wg
_______________________________________________
jakarta.ee-wg mailing list
jakarta.ee-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-wg