Consider changing TCK package to not start with jakarta package...

[scottmarlow]

Some Servlet container implementations may be confused by TCK test deployments in jakarta namespace which could lead to TCK challenges (click on platform discussion thread link for more details).

Would it take more than a few additional weeks to address this for 4.0? I'm trying to understand the impact on the EE 10 schedule and how much more time would be needed to avoid this potential issue.

How disruptive would a package change from jakarta to something else be to ongoing developers that have pending changes (via pending work not yet merged)?

The ^ discussion thread is too long to read but some messages that mention servlet conflicts with jakarta namespace are:

1. Mention of TomEE servlet container workaround for servlet classes in javax/jakarta namespace.
2. TomEE optimization to ignore jakarta classes.