| Re: [jms-dev] Preparing for final release |
Also, there's a TCK Results Summary already in place in OpenMQ. All it needs are the final pointers and it's good to go.
https://eclipse-ee4j.github.io/openmq/certifications/jakarta-messaging/3.0/TCK-Results
I believe GlassFish 6 RC1 contains the jms-api version is 3.0.0-RC1. Is that what we want? We can use Open MQ -- (for the ballot, that's perfectly good compatible implementation). This job here, runs the stand-alone TCK against Open MQ all by itself. However, we need to get the MetaData tests to pass by upgrading the TCK to use 3 as the expected API version and fix this issue.
-- Ed
On 10/20/2020 6:42 PM, David Blevins wrote:
It seems there's an RC1 of GlassFish we could use for the Compatible Implementation request we need to complete our PR:
- https://github.com/jakartaee/specifications/pull/256
Tomorrow I plan to hunt it down and see if we can get a TCK run against it using our promoted TCK. Assuming all that goes we'll, we should be good to prepare the certification request and once that is added to the GlassFish website, we can let the our mentor know to start the ballot.
Ideally we have a ballot up by Friday.
_______________________________________________ jms-dev mailing list jms-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jms-dev__;!!GqivPVa7Brio!L2SUzgn3sUFgsKQ8CxV6ka6uvUbtcjdtiKuFQ1avcrR1j7UwG-gyR2oExsCq88U$
_______________________________________________ jms-dev mailing list jms-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jms-dev__;!!GqivPVa7Brio!ILg2w9piLJIFjcgerm6KcOmAeiuRuvWHNhG0TWkXU31LtpnLtSrDNfBSNat7cOk$