>
>
> > Or for now generate 2 build artifacts? (as long as it is really just the
> > package rename)
> >
>
> Hm, no. I just tested locally Tomcat 10.0.1 with Apache Wicket (9.x,
> master). Nothing more.
> Tomcat 10.0.x is not production ready so it is too early to do anything
> about Jakarta APIs in Wicket.
> First we need to release Wicket 9.0.0 (with Javax APIs) and then we can
> start thinking about Jakarta APIs.
>
>
yes exactly, so many frameworks are going to do that (wait)
So not release any artifacts that use the new jakarta api's
So that means that for many people they can't start test or use Tomcat 10..
Because who is using plain servlet api only?
Any 3rd part dependency is your code that uses some javax.servlet package
needs to make a special release..
This will take ages, not to mention will only be really done for the latest
releases of those packages (like Wicket 9)
