| Re: [jakarta.ee-spec.committee] Agenda for the January 13th Jakarta EE Specification Committee call |
All,
I mentioned during the call yesterday that it shouldn't be very hard to produce the TCKs for EE 9.1. I wanted to share some more thoughts on that here. IMO, there are likely to be two (common) issues with running all of our TCKs on Java SE 11:
1. The TCK Signature test tooling is Java SE version specific
currently [1] which means the various teams that produce TCKs will
need to generate Java SE 11 signatures. The Platform TCK team has
already generated the Java SE 11 signatures but I don't believe
they have been verified yet.
2. There may be JDK runtime behavior changes between Java SE 8 + 11 that may require some TCK tests to be changed.
Also keep in mind that not of the TCKs are generated by the
Platform TCK, so we will need the additional teams to be engaged
to do the work.
In summary, the TCK teams will still be on the critical path but
probably not as much as the GlassFish team adding Java SE 11
support and testing with all of the required/optional TCK tests.
Scott
[1] https://github.com/eclipse-ee4j/jakartaee-tck/issues/156 "Need improved signature test tool that doesn't include JDK signatures"
The agenda for our committee call on Wednesday at 17:00 UTC is here. Please update and add items as required.
_______________________________________________ jakarta.ee-spec.committee mailing list jakarta.ee-spec.committee@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee