Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[messaging-dev] Releasing Messaging 3.1
  • From: Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx>
  • Date: Wed, 2 Mar 2022 11:09:01 +0000
  • Accept-language: en-GB, sk-SK, en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; 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=ZC+lplV4J0n8N4amyhY6Pdrm1jtCUkVazDsReKu9+0E=; b=SYAzJdu3mm+7+wca3MjojdjgkF8Zesifxt8aCSkMd1gNpbR0voFhpfwqQ6kA6n9IfkLgrEjBYk2ZImqZ99k20LMiuyNZQuir7lMk53PblESd5TnF7sQAUv2GKnP5YAL01erlq5nLdqFOxxJUX6+HTWMrcgDs1aZClJwB+nJQR0QmghUnkimxTA2Y+weRyn5jH5dbKFB3+KpjPS4bJnvtdDOlr/s+PGp5o/DrVfoXbz1tcrG6BKeXZPLsM9NmABOQOT/dw38eVChqxArKPVSJ4zBPdUdnIFrXcHxqDedsypBs/wZjf4snprIzsXDObguLaClc3ONqazqwxZx9x+qQrg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=eDoYuyivAWc8gUhEdd2AlCHdSs0JT9QtsJjlQy6gLVg7RlHPHt1gqYt8fJMn1w0nilxWbVn8CB0dzEQ7kcEnhOsELQprJDM/zsK+IBWcpedOI3izCd1kwiPJb8ke+cO/iXQ5e37bX9ulvFF7HlsaSNriG9qOLPk0aADdfSxzmtp+mruEJ43LhOQiZnA+nvxgkaJEqTvI0MIstC4dz/3D/gV54881pzlnqsqwz+NXYd2/y7iO91d3PjACYG6095Lq8neCjg9SZvstuFRPuYqlctrN0oXo0+VGyOI6Rf1fApleFtFwP96GdLOWQwg4ckrwhNsXRJvq0zt5eako9gdUrA==
  • Delivered-to: messaging-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Suggested_attachment_session_id: 46fcf1ce-c501-8db1-570a-732a966bbf7f
  • Thread-index: AQHYLh1fDIVSyk9nxkSdHB8Bk1a6tg==
  • Thread-topic: Releasing Messaging 3.1

Hi all,

I'm trying to release Messaging 3.1 this week and I realized there's no email thread dedicated to this so I'm starting this thread to keep information about the progress in one place for everybody involved.

Current status:

Messaging 3.1 API:
Messaging 3.1 TCK
  • Part of the Jakarta EE TCK
  • The TCK is regularly executed against GlassFish/OpenMQ in this Jenkins job
  • The tests modified to cover all the new functionality (only repeatable annotations)
  • The signature tests updated
  • The metadata tests updated
  • The standalone TCK guide still mentions 3.0 version, needs to be fixed (I plan to fix it today)
  • The latest TCK run failed on signature tests and metadata tests
  • 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
  • Upgraded Messaging API to 3.1
  • Needs to upgrade OpenMQ after a new OpenMQ version is released
OpenMQ and GlassFish teams, please, can you provide the status from your side and share your plans towards passing the Messaging 3.1 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 | | info@xxxxxxxxxxx | @Payara_Fish

Back to the top