This should have happened in last 10 years, but for some reason it didn't. Basically, if plugin explicitly (or implicitly) depends on maven-compat, it is still de facto a Maven2 plugin. In 2024. Go figure!
Thanks T On Tue, Apr 30, 2024, 23:30 Olivier Lamy <ol...@apache.org> wrote: > On Tue, 30 Apr 2024 at 15:56, Guillaume Nodet <gno...@apache.org> wrote: > > > > Maven-compat has been deprecated years ago, so the goal would be to get > rid > > of it. > > For months, efforts have been made to first make maven-compat completely > > optional. > > This is now the case in maven itself. > > However, some plugins still rely on it and they should be migrated to use > > Maven 3 apis. > > This is a required step before being able to get rid of maven-compat. > > > > I'm still hesitant about the time table, whether maven-compat should be > > removed from > > 4.0 distribution or not. It may be slightly premature, since a few > plugins > > still depend on it. > > > > if we could have at least core plugins (default lifecycle) ready, that > could work, but that's some work. > but do you have some timeline in mind for 4.0? or it's just whenever > it;s ready :) > > > > > Le mar. 30 avr. 2024 à 02:02, Olivier Lamy <ol...@apache.org> a écrit : > > > > > > Hi, > > > I can see plenty of PRs with maven-compat removal. > > > Maybe this could be explained and so more people could help for this > task? > > > > > > cheers > > > Olivier > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > -- > > ------------------------ > > Guillaume Nodet > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
