On Mon, Nov 4, 2019 at 9:54 AM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:
The biggest challenge may be getting the TCKs to run on JDK 11 rather than the apis. Has anybody tried this yet or has a handle on how big the effort?
The platform TCK signature tests  may need adjustment. Likely some changes may be needed in the ant scripts (or perhaps in ts.jte configuration) for adding additional command options when launching Java processes. Other TCK changes may also be needed, depending on how we want to handle testing of artifacts removed by jeps#320  in JDK 11. I'm not sure of the scope of effort to update the various TCK signatures for JDK11.
The various standalone TCKs may need changes as well.
The package rename and updating the TCKs for JDK 11, would likely need to be done in isolation, so that either change could be verified by passing a Jakarta EE 8 (using javax.* package) or Jakarta EE 9 (using jakarta.* package) implementation, with the TCKs.