[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [glassfish-dev] [openmq-dev] Releasing Messaging 3.1
|
On Wed, 2 Mar 2022 at 12:09, Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx> wrote:
>
> OpenMQ
>
> Upgraded Messaging to 3.1 (https://github.com/eclipse-ee4j/openmq/pull/1398)
>
> this should pass the signature tests
> I think that the JMS metadata still needs to be updated for ConnectionMetaData (I think in the ConnectionMetaDataAdapter)
It was updated in above PR 1398, and is included in M3 build.
> this should then pass all the metadata tests
It does indeed:
https://ci.eclipse.org/openmq/job/2_openmq-run-tck-against-staged-build/37/
the only failure was for signatures, as the TCK used:
*** 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-03-01 04:25:22.000000000 +0000, size(b):
14166201 ***
*** SHA256SUM: 0f3fc1ac079b495e06e56a68df377f1d91274dcb33bf4239e3abd9163d1dd73d
***
had no signatures updated yet.
> A new version of OpenMQ should be released to act as a CI for Messaging
I plan to do RC shortly. I suppose it will be almost identical to the
M3, but at this moment I'm not sure.
> Currently, the only role of GlassFish is to act as the CI because I think that the TCK Jenkins job runs against the OpenMQ bundled in GlassFish. If we can pass the TCK with plain OpenMQ, then we don't need GlassFish for releasing Messaging 3.1
I think for OpenMQ to be tested for CI - it's fine to pass 904 standalone tests.
I don't know if that's ok for Messaging Spec to have 2k+ EE tests
skipped. Maybe it is.
> Needs to upgrade OpenMQ after a new OpenMQ version is released
The latest OpenMQ with Messaging 3.1 has been integrated into GF
with https://github.com/eclipse-ee4j/glassfish/pull/23836.
--
Piotrek
