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
--------------------------------------------------- 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
Blevins <dblevins@xxxxxxxxxxxxx> To:
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx> Cc:
05:45 PM Subject:
Re: [jakartaee-platform-dev] CTS 8.0.1 and JSONB TCK 1.0.1 Sent
We don't have an established protocol
for handling updates like this. I propose the following as a bare
- 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.
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.