Just the maven coordinates. As for expected problems: probably folks have to update their poms to use the jakarta variants, but mostly they shouldn't bite if they use the provided scope.
For benefits: - the Jakarta group-id is the future, all servers will move to that maven coordinate - the licensing is now uniform (Eclipse) instead of whatever the spec lead thought was good - marketing: "Wicket has moved to use the Jakarta EE Maven artifacts, embracing the future of Java Enterprise software development" - hopefully the naming of the GAV will remain sane, instead of each spec lead using a different naming scheme (even across versions) Martijn On Fri, Jan 10, 2020 at 12:03 PM Martin Grigorov <mgrigo...@apache.org> wrote: > > Hi Emond, > > If it is just about different Maven coordinates then it is OK. > For the change javax.servlet -> jakarta.servlet it is too soon. > > On Fri, Jan 10, 2020 at 12:40 PM Emond Papegaaij <emond.papega...@gmail.com> > wrote: > > > Hi all, > > > > While building our application against Wicket 9, I noticed Wicket > > still uses the Java EE 8 APIs. I would like to change these to the > > Jakarta versions. The APIs themselves are completely identical, it is > > just the maven coordinate that changes. They do however come with a > > better license (Eclipse). What do you think? > > > > Best regards, > > Emond > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com
