Running

Common Configuration for all Tomcat versions

None

Tomcat 9.0.x

None required (clean 9.0.x build).

Tomcat 10.0.x

Remove the request-character-encoding and response-character-encoding settings from conf/web.xml (the JSP TCK has one test that depends on the default encoding).

Test Suite

Download one of the following:

• latest EE4j8 nightly buildJakarta EE 8 (Tomcat 9.0.x): httpshttp://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/jsptck-2.3_latest.ziplatest master nightly build: https://jenkinsjakartaee8/promoted/websocket-tck-1.1.1.zip
• Jakarta EE 9 (Tomcat 10.0.x): http://download.eclipse.org/ee4j/jakartaee-tck/jobmaster/standalonetck-nightly-build-run/lastSuccessfulBuild/artifact/standalone-bundles/jsptck-2.3_latest.zip/websocket-tck-2.0.0.zip (this will change once formally released)

Extract to JSP_TCK_HOME

Edit $JSP_HOME/bin/ts.jte

...

sigTestClasspath=${el.classes}${pathsep}${jspservlet.classes}${pathsep}${JAVA_HOME}/lib/rt.jarjar${pathsep}${JAVA_HOME}/lib/modules

set JAVA_HOME

cd $JSP_TCK_HOME/bin

...

A default 9.0.x build with the above configuration passes both the latest master and EE4J8 nightly buildsthe Jakarta EE 8 JSP TCK.

A default 10.0.x build with the above configuration passes the currently nightly build (as of 2020-05-26) of the Jakarta EE 9 JSP TCK with Java 8.

Fixed bugs

The Apache Tomcat project has reported the following bugs to the Eclipse Jakarta EE TCK project which have since been fixed in the latest nightly builds.

• 1 x signature test
  • https://github.com/eclipse-ee4j/jakartaee-tck/issues/48

...