Mark,
On 7/23/24 03:05, Mark Thomas wrote:
On 22/07/2024 23:33, Christopher Schultz wrote:
Mark,
On 7/22/24 12:53, Mark Thomas wrote:
All,
Today I have configured the tomcat-tck repository to run the EL,
Servlet, Pages and WebSocket TCKs once every day for all combinations
of JDK 17 & 21, Ubuntu latest, MacOS latest and Windows latest using
GitHub actions.
There were a few issues to iron out but these should now all be
resolved.
The TCK will run at just after 08.00 UTC every day and it will use
the latest Tomcat 11 SNAPSHOT (these are updated on every commit by
buildbot).
Windows seems to take a little longer than the others but the full
TCK run (all four TCKs) is complete in just under 25 minutes.
Considering it used to take longer than that to run any of the old
TCKs, kudos to the Jakarta EE folks that have been working on the
refactoring.
Tomcat 11.0.x currently passes the TCK (as it should).
I have no plans to formally certify Tomcat as passing the TCK over
and above what I have already completed as part of the release
process for each of the specifications (the specification release
process requires at least one compatible implementation).
Nice work.
My guess is that getting Tomcat to be formally-certified would take
(1) money (2) politics and (3) other stuff nobody wants to deal with
any time soon.
For certification the bar is pretty low. It would probably take longer
on the Eclipse side getting the certified version added to the various
websites than it would be on the ASF side doing the actual certification.
Whether even that low level of effort is something we want to do is TBD.
There is very little (no?) demand from users for formal certification.
The real value to me is in running and passing the tests. Therefore,
I'll probably use the tomcat-tck repo to test each release candidate as
it is published and include those results in my vote. I haven't figured
out how to automate that but I am thinking about it.
If we want to use the "Jakarta EE compatible" logo then that is where we
hit your points 1, 2 and 3 in spades.
We'd need to sign a trademark agreement and my reading of that is that
the ASF does not currently have the right membership of Eclipse to be
able to use the logo. Fixing that looks likely to take some time and
politics to resolve - particularly since the ASF is unlikely to want to
pay for am Eclipse membership.
Given that we are free to make factual statements such as "Tomcat 11.0.x
passes the latest Annotations, EL, Pages, Servlet and WebSocket TCKs" or
"Tomcat 11.0.0-M20 is a compatible implementation of the Jakarta Servlet
6.0 specification" I'm not at all convinced of the need to use a logo.
It looks like we might be able to get a pass... sort of.
From [1]:
"
Use of the “Jakarta EE Compatible” mark is limited to use in conjunction
with Compatible Software Products (as defined below) distributed by:
Participant, Enterprise or Strategic Members of the Jakarta EE WG
who are also licensees under the Jakarta EE Compatibility
Trademark License Agreement; or
Guest Members of the Jakarta EE WG, if:
Use of the Jakarta EE Compatible mark is approved unanimously by
the Jakarta EE WG Steering Committee; and Such Guest Members
are also licensees under the Eclipse Foundation Trademark
License.
"
So we would need to be a licensee of their trademark license. We could
ask to become a "Guest Member" of the Jakarta EE WG. I don't know what
that entails.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
