Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [jakarta.ee-spec.committee] CTS 8.0.1 and JSONB TCK 1.0.1
This is an updated TCK for a JSON-B challenge from Open Liberty.  Notice the increase in the third digit -- CTS TCK 8.0.1 and JSON-B TCK 1.0.1.  If you are currently testing with the CTS TCK 8.0.0 and JSON-B TCK 1.0.0, you are still good.  As long as you identify which TCK you are executing against in your CR and TCK Results, you are good.  

As far as minimum set of tests...  Depends on what type of "certification" you are shooting for...  As an example, Open Liberty's immediate goal is to be Full Platform compliant by 9/10.  We also hope to be Web Profile compliant by then, but we're hitting another hiccup with the TCK.  Eventually, Open Liberty will also run the individual TCKs to be Component compliant -- but, that will be after the 9/10 deadline.  

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:        "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
To:        Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>, jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc:        "jakartaee-platform-dev-bounces@xxxxxxxxxxx" <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
Date:        09/06/2019 04:13 AM
Subject:        [EXTERNAL] Re: [jakarta.ee-spec.committee] [jakartaee-platform-dev] CTS        8.0.1        and JSONB TCK 1.0.1
Sent by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx


OK I’m confused now. We are well down the CTS testing and do we have to switch to this version?

 

Also what is the minimum set of tests that need to be run to meet the compatibility requirements. We’ve been running all the standalone TCKs as well as the Full Platform?

 

Steve

 

From:jakarta.ee-spec.committee-bounces@xxxxxxxxxxx <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> On Behalf Of Kevin Sutter
Sent: 06 September 2019 00:10
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: jakarta.ee-spec.committee@xxxxxxxxxxx; jakartaee-platform-dev-bounces@xxxxxxxxxxx
Subject: Re: [jakarta.ee-spec.committee] [jakartaee-platform-dev] CTS 8.0.1 and JSONB TCK 1.0.1

 

We are struggling to get the overall CTS 8.0.1 tested in time for the Certification Requests.  Since we have not run the standalone JSON-B TCK in the past, I have no idea how involved that is and I can't commit to running that bucket.  But, we are running the Full Platform and (hopefully) the Web Profile TCKs...

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx    Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:        David Blevins <dblevins@xxxxxxxxxxxxx>
To:        jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc:        jakarta.ee-spec.committee@xxxxxxxxxxx
Date:        09/05/2019 05:45 PM
Subject:        [EXTERNAL] Re: [jakartaee-platform-dev] CTS 8.0.1 and JSONB TCK 1.0.1
Sent by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx




We don't have an established protocol for handling updates like this.  I propose the following as a bare minimum:

- JSONB 1.0.1: We get TCK verifications from *both* GlassFish 5.1 and OpenLiberty in the form of JSONB certification requests against the new sha256.  We then publish immediately.  I published the 1.0.0 TCK moments ago, so I'm happy to do that.

- CTS 8.0.1: We get TCK verifications from *both* GlassFish 5.1 and OpenLiberty in the form of Full and Web Profile certification requests against the new sha256.  We hold the binaries, add this additional TCK link and certification requests to the Web and Full PRs.  We publish all TCKs when the votes complete.


--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com


On Sep 5, 2019, at 3:34 PM, Gurunandan Rao <gurunandan.rao@xxxxxxxxxx> wrote:

Hi all,
We have updated CTS, to exclude JSONB tests accepted in TCK challenge described inhttps://github.com/eclipse-ee4j/jsonb-api/issues/180
Also we have created new bundle for JSONB TCK with excluded tests. Please refer the below download location for the new bundles.

1. EFTL :
CTS 8.0.1 - http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8-eftl/staged-801/eclipse-jakartaeetck-8.0.1.zip
JSONB TCK 1.0.1 - http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8-eftl/staged-801/eclipse-jsonb-tck-1.0.1.zip

2. EPL :
CTS 8.0.1 - http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8/nightly-801/jakartaeetck-8.0.1.zip
JSONB TCK 1.0.1 - http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8/nightly-801/jsonb-tck-1.0.1.zip

regards,
Guru


_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee


Back to the top