Hi,
"
mv jakarta.jakartaee-api-9.0.0-RC1.jar
$GF_HOME/glassfish5/glassfish/modules
"
I can see that jakarta.jakartaee-api-9.0.0-RC1.jar contains
jakarta.ejb.* classes, but I suspect that we need to do more
for switching to build the TCK with use of jakarta.ejb in TCK
sources, as the nightly build compile step fails to import
jakarta.ejb classes:
"
compile:
[ts.javac] Compiling 65 source files to /home/jenkins/agent/workspace/jakartaee-tck_master/classes
[ts.javac] Picked up JAVA_TOOL_OPTIONS: -Xmx6G
[ts.javac] /home/jenkins/agent/workspace/jakartaee-tck_master/src/com/sun/ts/tests/interop/csiv2/common/CSIv2AppClient.java:25: error: package jakarta.ejb does not exist
[ts.javac] import jakarta.ejb.*;
"
Should we replace {ri.modules}/jakarta.ejb-api.jar in the ts.jte with jakarta.jakartaee-api-9.0.0-RC1.jar (either in the Jenkins job or via change to ts.jte)?
Will the GlassFish jakarta.jakartaee-api always contain all
of the spec api classes? If yes, then it may work to update
ts.jte to use that (once all of the javax references are
changed to jakarta namespace).
Scott