On Wed, Mar 4, 2020 at 4:02 PM Johan Compagner <jcompag...@servoy.com> wrote:
> > > > > > > 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) > There is no official release of Jakarta EE 9 yet! I didn't even bother to replace javax.servlet:servlet-api Maven dependency with the Jakarta one in Wicket. I just used https://github.com/apache/tomcat-jakartaee-migration to migrate (already built) wicket-examples.war and it worked fine! Later I tried to do the same with a Spring Boot based application but the migration tool faced some problems with the nested archives in Boot's special packaging. Tomcat 10.0.x is for early adopters to test it and report issues. But as Chris suggested we should make this more clear in the docs! I've committed some improvements. If anyone have more ideas for improvement I'll be happy to apply them! :-)
