Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [messaging-dev] Help/guidance with the 3.1 release needed


On Thu, Feb 24, 2022 at 12:58 PM Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx> wrote:
Hi, thanks all for your hints.

I'll connect with the OpenMQ/GlassFish team to integrate it and try passing the TCK.

The TCK script as it's currently there hasn't been updated to EE 10 yet, so that would be a start. I recently learned from Piotr that the TCK is actually not testing GlassFish directly, but runs against the openmq distribution that's within GlassFish. 

To make the script from the point of view of TCK testing the API really work, we may have it update the Messaging API within the [glassfish]/mq instead of [glassfish]/glassfish/modules.

Kind regards,


Kind regards,

Ondrej Mihályi

Senior Payara Service Engineer
Payara - Supported Enterprise Software for Jakarta EE and MicroProfile Applications
US: +1 415 523 0175 | UK: +44 207 754 0481


Payara is a proud recipient of the prestigious Queen's Award for Enterprise: International Trade 2021

Payara-Tech LDA, Registered Office: Rua Nova de São Pedro no. 54, 2nd floor, room “D”, 9000 048 Funchal, Ilha da Madeira, Portugal

VAT: PT 515158674 | | info@xxxxxxxxxxx | @Payara_Fish

From: messaging-dev <messaging-dev-bounces@xxxxxxxxxxx> on behalf of Piotr Żygieło <piotr.zygielo@xxxxxxxxx>
Sent: 23 February 2022 18:36
To: EE4J Messaging project developer discussions <messaging-dev@xxxxxxxxxxx>
Subject: Re: [messaging-dev] Help/guidance with the 3.1 release needed
On Wed, 23 Feb 2022 at 18:23, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
> The release of the actual artefacts should only be done after the ballot has concluded successfully,
Release to central - right.

> so for the moment jenkins is not needed.

How can JMS 3.1 find its way to staging repo then?

> When it's time to release, it's a matter of staging using job:
> 1_messaging-build-and-stage

I believe this 1_*, updated on Jenkins to use java 11+, has to be
executed for at least RC in the first place. Only then can it be
integrated by downstreams, from staging repo. Without such integration
I doubt the ballot would conclude at all...

The job 3_* - this one can wait, but I don't think 1_* can.

Please, please - I'm asking for any output from messaging since

messaging-dev mailing list
To unsubscribe from this list, visit
messaging-dev mailing list
To unsubscribe from this list, visit

Back to the top