It is. I was referring to Eclipse GlassFish 5.2, as in the previous
paragraph.
Kevin Sutter wrote on 3/15/19 1:08 PM:
> (Of course, assuming Eclipse GlassFish
intends to be certified as Java EE 8 compatible, it will
also need to run the official Oracle TCKs for all the Java
EE 8 APIs as well.)
I thought Eclipse Glassfish 5.1 was Java EE 8
compatible?
-----
Original message -----
From: Bill Shannon <bill.shannon@xxxxxxxxxx>
Sent by: jakartaee-tck-dev-bounces@xxxxxxxxxxx
To: jakartaee-tck developer discussions
<jakartaee-tck-dev@xxxxxxxxxxx>, Lance Andersen
<lance.andersen@xxxxxxxxxx>
Cc:
Subject: Re: [jakartaee-tck-dev] What is the plan for building
jaxb-tck?
Date: Fri, Mar 15, 2019 2:50 PM
Lance Andersen wrote on 3/15/19 11:04 AM:
For Java EE 8 and below, if an app server is not using
the JAXB provided by Java SE and is including an
implementation, the running of the JAXB TCK is required to
validate the implementation is compliant.
To be clear, that would be the official licensed from Oracle
JAXB TCK, not the JAXB TCK contributed to the Eclipse
Foundation. The Eclipse Foundation has licensed the official
JAXB TCK, so this should not be an issue, but I want to make
sure there's no confusion over which TCK needs to be run.
Note that this applies to the upcoming release of Eclipse
GlassFish 5.2, and to any other product providing an
implementation of JAXB on Java SE 8.
(Of course, assuming Eclipse GlassFish intends to be certified
as Java EE 8 compatible, it will also need to run the official
Oracle TCKs for all the Java EE 8 APIs as well.)
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
|