|Re: [jakartaee-tck-dev] How to build the Platform TCK to target JDK8 but support running with JDK11?|
On 6/30/20 3:39 PM, Kevin Sutter wrote:
If Glassfish is not interested in Java 8, how are we going to determine whether the TCK is executable and testable with Java 8?
We will not be able to determine whether the final GlassFish 6.0 release passes all tests on 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?
IMO, we need to question what it is that we want exactly.1. One final EE 9 release that includes verification that the TCKs are executable and testable with Java 8 and Java 11.
2. A final EE 9 release that includes verification that the TCKs are executable and testable with Java 11 and a later (Platform 9.1.0 + respective standalone) minor release that includes verification that the TCKs are executable and testable with both Java 8 + 11.
Or, do we wait until a vendor tries the Java 8 compliance testing and then work through the problems?
Good question, IMO, I think that option #2 above is better, but I defer to conclusions to be made on platform mailing list discussion and/or steering committee decisions.
With option #2, if we do come up with a way to test TCKs on Java 8 and they pass 100% before EE 9 is final, then we will have achieved option #1 in an unplanned way but that would be best (e.g. we will definitely consume fewer Jenkins CI resources as well).
This might get messy if we have to modify some tests after we go final with Java 11...
Yes, agreed. Also, with option #2 above, this will impact some of the community desire to start reorganizing the 5 million+ lines in the Platform TCK for EE 10.
I don't have all the answers. Just questions to think about and figure out before we claim Jakarta EE 9 is done...
Thanks Kevin for raising these questions! Scott
Back to the top