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
  • From: Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx>
  • Date: Thu, 24 Feb 2022 11:58:28 +0000
  • Accept-language: en-GB, sk-SK, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=payara.fish; dmarc=pass action=none header.from=payara.fish; dkim=pass header.d=payara.fish; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=We8+B1lPaKKf1St3hOeSAM+v0EIZr7zf0nQyxKDh4O4=; b=Qai8MoKrNLa7xqNVKUHpaMNxkfRYw3Wa/3+EVuwzm2v/RvyC80FbJ2/7CeNH8yZwM9bS72JIGJSDeCNZM9l2e0x23ZGUJe4B5KDhMTWJBPiKEDSx+ZtP+mTEkc0MbuyX0RN4aspEhyiWpIaKuz+uLY7SqnIBB1c2Jlkk1sEbnHD6J6wppcBWM0+uFaMt+Qf+DtVerEoUS7BofMNOOPf+JqbM8EIFyLiAtXzoZCANf8W7jyDOHXAjK1IwH8+VQR43Wln4SZ89uPbaWMVjTgwjNEb6ad6nM05nEBOP3Pa7HAb7WYdDl0mKMLXiru/rrLEAHTfHgXxFLUxWteEJrmugTQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=T/hZN+vc8ujURLK75+j82Gc15UFC7IPB6za6+OVyYLyTNSSzd+o2JOCkxNFjRD2J2ns5zglDsFUuYjE2N+8HKMBxfO9dGOC8WkcH7Rhk7BvVFYmyT85wxS/wzDNl7zs/WeB6EpQ1rtcYN75Me1SR7jEvZirXYWu4I5W5xCN+6pIFVp1LfWV5/cN65WwXKXdy7jSXI76HgWvhzhndP/eQbs0ZIU/NGjjnEmKw4ElzFSDupDrHM4ce8AQkBUjhlsHXlBmIip5W0db5Cu7hWGvt4SelQw4gyOREHbNaJJCtM9TAVFMPvVJX/Yd1GFyg0krOElfeReXgaLGcWbmVo7Dqqw==
  • Delivered-to: messaging-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/messaging-dev/>
  • List-help: <mailto:messaging-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/messaging-dev>, <mailto:messaging-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/messaging-dev>, <mailto:messaging-dev-request@eclipse.org?subject=unsubscribe>
  • Suggested_attachment_session_id: 757ad8af-e10b-cfd2-8f64-81f9a6f3e1f3
  • Thread-index: AQHYKKfBPmNdEUs0DUWKBccJB3YUsayhYrwAgAADugCAAS28RQ==
  • Thread-topic: [messaging-dev] Help/guidance with the 3.1 release needed
Hi, thanks all for your hints.

I found out that the 1_messaging-build-and-stage job will create a release branch and tag and stage artifacts in the staging repository.

So I triggered the job and it created 3.1 artifacts in the staging repository here: https://jakarta.oss.sonatype.org/content/groups/staging/jakarta/jms/jakarta.jms-api/3.1.0/

These artifacts can be already used by implementations to integrate the new API.

There's still a small glitch that the Jenkins CI github user doesn't have permissions to push changes to github after the repo was moved under jakartaee org, I've raised an issue with Eclipse here: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/940. But it didn't block deploying the artifacts to Nexus.

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


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 | www.payara.fish | 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
https://www.eclipse.org/lists/messaging-dev/msg00031.html...

Piotrek
_______________________________________________
messaging-dev mailing list
messaging-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

Back to the top