Scott, Now we have two
threads going on this topic... :-) That's okay, I'll try to keep
Glassfish plan to be compliant with Java 8? The last I heard, they
were only looking to be compliant with Java 11. If Glassfish is not
interested in Java 8, how are we going to determine whether the TCK is
executable and testable with Java 8? Since the Java 8 compliance
is optional, is this additional testing and verification required before
we can claim Jakarta EE 9 is complete? Or, do we wait until a vendor
tries the Java 8 compliance testing and then work through the problems?
This might get messy if we have to modify some tests after we go
final with Java 11... I don't have all the answers. Just questions
to think about and figure out before we claim Jakarta EE 9 is done...
Thanks for raising
this topic! --------------------------------------------------- Kevin Sutter STSM, MicroProfile and Jakarta EE architect @ IBM e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter
Marlow <smarlow@xxxxxxxxxx> To:
Joseph <alwin.joseph@xxxxxxxxxx>, jakartaee-tck developer discussions
Re: [jakartaee-tck-dev] How to build the Platform TCK to target JDK8 but
support running with JDK11? Sent
Thanks for raising these points! :-)
On 6/30/20 1:52 PM, Alwin Joseph wrote: > Hi Scott, > > Can you please help confirm or correct me on the below 2 statements. > > 1. The final TCK bundle should be built with JDK11 only. We will not
> build the platform TCK using JDK8.
We should target generating JDK8 classes, so that compatible implementations may also run with JDK8.
For inclusion in Jakarta EE 9, specification’s APIs MUST be compiled at
the Java SE 8 source level. However, compatible implementations of the
Jakarta EE 9 Web Profile and Full Profile MUST certify compatibility on
Java SE 11. Compatible Implementations MAY additionally certify and support Java SE 8. "
Excellent point to raise, the hard requirement is that our build generates JDK8 classes, although we could also generate separate JDK8 +
JDK11 TCK bundles.
IMO, we could stick with building with JDK8, which is less work than switching to building with JDK11. I will update the $subject to reflect
this point. :)
> 2. The final TCK bundle should be used to run tests on both JDK8 &
We must run/pass the final TCK bundle on JDK11, as per above linked JakartaEE9ReleasePlan.
Since we expect that EE 9 compatible implementations could also run on
JDK 8, I think that we should also run against JDK8 ourselves (so that
we know that its possible). IMO, we should next focus on passing
completely with JDK11, so that we finish that first. Then, we should
also pass completely with JDK8.