| Re: [openmq-dev] [glassfish-dev] Messaging 3.1 API artifact available in Nexus staging repo |
Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx> wrote:
> I've released Messaging 3.1 API artifacts in the Eclipse staging repository
> Can you have a look at them and try to integrate into GlassFish and OpenMQ snapshots that target EE 10?
Current
*** TCK bundle information
***
*** Name: jakarta-messaging-tck-3.1.0.zip
***
*** Bundle Copied to URL:
http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl//jakarta-messaging-tck-3.1.0.zip
***
*** Date and size: date: 2022-02-22 10:07:14.000000000 +0000, size(b):
14166240 ***
*** SHA256SUM: 9fcc4446303f0f35a3891a7cf066d133fa1b59abfa180e4411cea8363ce77581
***
was used to test OpenMQ with Messaging 3.1 API
(https://github.com/eclipse-ee4j/openmq/actions/runs/1894494362)
As expected - JMSSigTest failed, as it needs an update in TCK.
But - what just happened here?
From https://github.com/jakartaee/messaging
+ f1fa630...027e4da 3.1.0 -> upstream/3.1.0 (forced update)
t [tag update] 3.1.0-RELEASE -> 3.1.0-RELEASE
This was even staged (but is invisible in merged view as previous
3.1.0 was not dropped).
--
Piotrek