Re: [jms-dev] Preparing for final release

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [jms-dev] Preparing for final release

From: Ed Bratt <ed.bratt@xxxxxxxxxx>
Date: Tue, 20 Oct 2020 20:53:49 -0700
Delivered-to: jms-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jms-dev>
List-help: <mailto:jms-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jms-dev>, <mailto:jms-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jms-dev>, <mailto:jms-dev-request@eclipse.org?subject=unsubscribe>
Organization: Oracle Corporation
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1

Also, there's a TCK Results Summary already in place in OpenMQ. All it needs are the final pointers and it's good to go.

https://eclipse-ee4j.github.io/openmq/certifications/jakarta-messaging/3.0/TCK-Results

On 10/20/2020 8:48 PM, Ed Bratt wrote:

I believe GlassFish 6 RC1 contains the jms-api version is 3.0.0-RC1. Is that what we want? We can use Open MQ -- (for the ballot, that's perfectly good compatible implementation). This job here, runs the stand-alone TCK against Open MQ all by itself. However, we need to get the MetaData tests to pass by upgrading the TCK to use 3 as the expected API version and fix this issue.

-- Ed

References:
- [jms-dev] Preparing for final release
  - From: David Blevins
- Re: [jms-dev] Preparing for final release
  - From: Ed Bratt

Prev by Date: Re: [jms-dev] Preparing for final release
Next by Date: Re: [jms-dev] Preparing for final release
Previous by thread: Re: [jms-dev] Preparing for final release
Next by thread: Re: [jms-dev] Preparing for final release
Index(es):
- Date
- Thread

Breadcrumbs