On Mon, Nov 23, 2020, 17:07 Mark Thomas <ma...@apache.org> wrote: > Hi all, > > Now that the final versions of the TCKs for Jakarta 9 are available I've > been running them against the current 10.0.x (effectively 10.0.0-M10). > > The results can be summarised as: > > Expression Language > - Passes apart from the API signature test because we use BND > annotations for JPMS support > > Websocket > - Passes apart from the API signature test because we use BND > annotations for JPMS support > > Servlet > - Passes apart from the default context path test because Tomcat > deliberately always overrides the associated web.xml setting > > JSP > - Passes > > All of the above were tested with both Java 8 and Java 11. > > The BND failures are not a concern as the annotations have no impact at > runtime. > > The Servlet failure is not a concern as Tomcat's behaviour is spec > compliant. The spec allows implementations to override the web.xml > setting and Tomcat will always do this. > > It is worth noting the Jakarta EE 9 only targetted Java 8. Current > planning is that a Jakarta EE 9.1 release will target Java 11 support > (while retaining Java 8 compatibility). This is essentially
What exactly does this mean? EE 9.1 will use multi-versioned classes? Or something else? a no-op for > Tomcat 10. We already have this and more. Tomcat runs on all current > versions of the JRE including the Java 16 early access releases. > > In summary, Tomcat 10 is in excellent shape. > > Given the alpha/beta/stable definition from [1], 10.0.x now clearly > meets the criteria for beta and some may consider it meets the criteria > for stable. With that in mind the next 10.0.x release vote will include > options for broken, beta and stable. > Awesome! > Mark > > > [1] http://tomcat.apache.org/whichversion.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
