| Re: [glassfish-dev] Messaging 3.1 API artifact available in Nexus staging repo |
On Tue, 1 Mar 2022 at 12:42, Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx> wrote: > > I'm in the process of releasing Messaging 3.1 and for that I've submitted a certification request for GlassFish 7 Milestone 2: https://github.com/jakartaee/messaging/issues/321 > > I ran the standalone TCK using a Jenkins job (https://ci.eclipse.org/messaging/job/2_messaging-run-tck-against-staged-build/12/) and the TCK passed. Just to make it clear - against "private" https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck-scottmarlow/job/OndroMih-jms-299-300-tests-repeated-annotations/3/artifact/standalone-bundles/messaging-tck-3.1.0.zip But do not be misled. - TCK has not updated signature file yet, - Scott's bundle has no PR 825 I suppose and yet - the sig test and metadata/version tests passed because: - OpenMQ in GF-M2 has no JMS3.1, but 3.0 still GF 7M2 isn't JMS 3.1 compliant, and I find this certification request premature. -- Piotrek