Hi Richard, On Thu, Mar 5, 2020 at 4:42 AM Richard Huntrods <huntr...@athabascau.ca> wrote:
> > On 3/4/2020 6:28 AM, Martin Grigorov wrote: > > 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! :-) > > Thank you for that Martin. I installed 10.0.x today, and as expected it > broke because all my servlets are based on javax. I grabbed a copy of > the migration tool. Sadly (for me) it required Maven to build, but after > some hesitency, I grabbed Maven and installed that (it was really easy). > Thank you for the feedback! I've added Maven Wrapper script to the project so that it is easier for non-Maven users like you to build the migration tool without much hesitency! ;-) https://github.com/apache/tomcat-jakartaee-migration/commit/198e510a67cec569e91cc2cc87e4f4adb181f753 Martin > > With Maven installed and working, I built the migration tool. Again, > easy. With the tool built I simply converted both of my application's > war files, copied them over the originals in webapps, started TC 10 and > everything worked! > > So I guess I'm "ready" for TC10 now. :-) > > -R > > > -- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > -- > This communication is intended for the use of the recipient to whom it is > addressed, and may contain confidential, personal, and or privileged > information. Please contact us immediately if you are not the intended > recipient of this communication, and do not copy, distribute, or take > action relying on it. Any communications received in error, or subsequent > reply, should be deleted or destroyed. > --- >
