Gurunandan Rao

Concurrency TCK failures with latest glassfish nightly build

33

Following Concurrency TCK failures with latest Glassfish 7 nightly Web Profile build: - ee.jakarta.tck.concurrent.spec.ManagedExecutorService.resourcedef.ManagedExecutorDefinitionWebTests.testCopyCompletableFutureEJB CI run - https://ci.eclipse.org/jakartaee-tck/job/10/job/jakarta-concurrency-tck-glassfish-run/95/

glassfish 7 web-profile bundle is missing concurrency jar, which causes signature test failure for Platform TCK Web Profile run. CI run:https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/1861/testReport/junit/com.sun.ts.tests.signaturetest.javaee/JavaEESigTest/jakartaeetck_run___signaturetest_javaee___signatureTest_from_jsp/

upgrade to latest cdi, EL api and Weld.

2

Signed-off-by: gurunrao upgrade to latest cdi, EL api and Weld.

remove references to JavaTest from TCK user-guide. Signed-off-by: gurunrao

TCK Migration: Move standalone jsonb tck signature tests from jakartaee-tck

3

TCK Migration: Move standalone jsonb tck signature tests from jakartaee-tck to https://github.com/eclipse-ee4j/jsonb-api and run with migrated TCK at https://github.com/eclipse-ee4j/jsonb-api.