Running

Common Configuration for all Tomcat versions

None.

Note: If you re-run the TCK you must stop Tomcat, empty the work directory and then restart Tomcat. This is because the TCK assumes it is running for the first time and a number of tests check various compilation activities.

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 latest nightly buildhttpsone of the following:

• Jakarta EE 8 (Tomcat 9.0.x): http://download.eclipse.org/ee4j/jakartaee-tck

...

• /jakartaee8/promoted/pages-tck-2.3.0.zip
• Jakarta EE 9 (Tomcat 10.0.x): https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee9/promoted/pages-tck-3.0.0.zip

Extract to JSP_TCK_HOME

Edit $JSP_HOME/bin/ts.jte

...

el.classes=${webServerHome}/lib/el-api.jar${pathsep}${webServerHome}/modules/jasper-el.jar

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

...

Accept the defaults and then run the tests

Expected results

A default 9.0.x build with the above configuration triggers TBD test failurespasses the Jakarta EE 8 JSP TCK.

A default 10.0.x build with the above configuration passes the Jakarta EE 9 JSP TCK with the following JREs:

• Adopt OpenJDK 8u275 b01
• Adopt OpenJDK 11.0.9 b11 (TCK and Tomcat)

Fixed bugs

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

• 1 x regressions
  • https://github.com/eclipse-ee4j/jakartaee-tck/issues/535 (PR to fix - https://github.com/eclipse-ee4j/jakartaee-tck/pull/536)
• 1 x signature test
  • https://github.com/eclipse-ee4j/jakartaee-tck/issues/48
  • https://github.com/eclipse-ee4j/jakartaee-tck/issues/294 (PR to fix - https://github.com/eclipse-ee4j/jakartaee-tck/pull/295)