> > > > > And then I don't care too much about if it goes from javax.servlet to > > jakarta.servlet or the other way around.. I just want to support both > > deployments. That our customers can dump in the generated war by our > > tooling in any tomcat version (8,9 or 10) and it just works. > > There has been talk of integrating the migration tool into Tomcat 10 so > if you drop in a Java EE 8 app it automagically converts it to Jakarta > EE 9 before starting it. > > I'm guessing you'd prefer this to having to provide separate Java EE and > Jakarta EE versions (even if all you had to do to create the Jakarta EE > version was run it through the migration tool). > > On a related topic, it would be helpful to know if the migration tool > successfully converts your app. >
yes i have been reading it up, so our customers could just use the migration app if they really want the WAR (that our tool generates) to deploy on 10 We don't use many fancy things like very "new" servlet or jsp things its quite basic servlets and filters + websocket stuff that also run fine under tomcat 8.. But i will do some test how that migration tool work. for me building it from maven is fine, but most of our customers dont code java or use mvn so are there plans to really make releases of it? so you can just download the shaded jar? -- Johan Compagner Servoy
