The current TCK source state, is that some changes have been made but we need to change the remaining javax.* references in the TCK, then we should be able to build the Platform TCK, without getting compile failures. More inline below.
I'm making the TCK repo changes for javaxmail and javax.activation.
It would be good if I could at least build the repo with the changes,
so first some stupid questions. I'm looking at the build instructions here:
https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Instructions-for-building-and-running-JakartaEE-TCK-bundle
It appears that the build depends on a version of GlassFish. (Shouldn't
it just depend on the API jar file?)
Yes, we are getting an early build of an GlassFish API jar file that has all of the package changes to jakarta.*, via above mentioned jakarta.jakartaee-api-9.0.0-RC1.jar.
So obviously I need a version of
GlassFish that includes the updates for javax.mail and javax.activation,
which luckily I have.
Can I just point the build at this version of GlassFish, per the instructions
above, and expect it to build?
We don't yet have a build of full (using jakarta.* package) GlassFish yet, so we cannot do any TCK testing.
(I assume no one else can build the TCK using this version of GlassFish
because the build would fail without the javax.mail and javax.activation
changes, right?)
Currently, the nightly Platform TCK build is getting compile errors because we didn't finish switching to jakarta.* namespace yet.
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev