|Re: [jms-dev] Preparing for final release|
This was discovered while running the Standalone JMS TCK with ActiveMQ. We didn't notice this before as GlassFish appears to still be returning `2.0` instead of `3.0`.
On 10/20/20 9: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 <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. -- David Blevins http://twitter.com/dblevins <http://twitter.com/dblevins> http://www.tomitribe.com _______________________________________________ jms-dev mailing list jms-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jms-dev
Back to the top