You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you proceed through the Tags ballot process, ^ is good to discuss with your mentor as well.
For the platforms do we just need to list whatever platform is actually used when the tests are executed? If that's the case then it just depends on who executes the TCK once we have something available for testing.
Makes sense.
I believe previously for Tags 2.0 we used Glassfish as the compatible implemented so my plan would be to do the same this go around for Tags 3.0.
I think that would need to be a milestone release build of the Tags 3.0 compatible implementation, GlassFish 7.0 seems like a fine choice but it really could be any (open source) Tags 3.0 compatible implementation that is publicly available in a milestone release form.
Can we have a TCK run for Tags now that the Jakarta Tags 3.0.0 api/impl has been staged? I saw that there were a few failures in the last run for JDK 17 (but they looked related to JSP/EL). I didn't get a chance to view the JDK 11 logs.
Once we have a finalized release, we need to run the TCK and publish the results. Suggestion below recommends using GlassFish 7.0 for the build.
https://jakarta.ee/specifications/tags/2.0/ shows that https://github.com/eclipse-ee4j/glassfish/releases/download/6.0.0-M3-2020-10-04/glassfish-6.0.0-M3-2020-10-04.zip was used for verifying Tags 2.0. I imagine that the first available Tags 3.0 implementation could be used to validate the Tags 3.0 release. As to the how or who can run that, IMO, whomever that is, they need to push the TCK results to a publicly available location and identify the publicly available Tags implementation (and version) and include the implementation download link (as per https://jakarta.ee/committees/specification/tckprocess/).
As you proceed through the Tags ballot process, ^ is good to discuss with your mentor as well.
Makes sense.
I think that would need to be a milestone release build of the Tags 3.0 compatible implementation, GlassFish 7.0 seems like a fine choice but it really could be any (open source) Tags 3.0 compatible implementation that is publicly available in a milestone release form.
Originally posted by @scottmarlow in #132 (comment)
The text was updated successfully, but these errors were encountered: