As Guillaume said, the time table of _actual removal_ from Maven (4) Core is still questionable. OTOH, we do want to _ensure_ that at least Maven Core Plugins are maven-compat free...
Personal (biased) opinion: given how much of the plugin that claims itself to be Maven3 plugin depends on maven-compat (explicitly or implicitly), Maven 4.0 is most probably too early to remove it, DESPITE we talk about maven-compat, a module that offers Maven2 compatibility layer. OTOH, the _presence_ of this module is becoming an impediment for us, and we do want to get rid of it, the sooner the better. On a related note: users who were against Maven 3.9.x emitting warnings about deprecated plugins... They "won", all the "Maven 3.9 should prepare for 4.0 work stopped", and this is the price now: it is not simple to detect these plugins in the wild. I understand "they (users) cannot do anything about warnings", but that could be at least "they (users) live with warnings and report deprecation issues to authors of deprecated plugins"... Currently we really have no clue how many affected (non-core) Maven plugins could be out there, that would simply break, if maven-compat would be removed. Thanks T On Wed, May 1, 2024 at 12:32 AM Basil Crow <m...@basilcrow.com> wrote: > On Tue, Apr 30, 2024 at 2:42 PM Tamás Cservenák <ta...@cservenak.net> > wrote: > > > > This should have happened in last 10 years, but for some reason it > didn't. > > Does the Maven project have a plan for ensuring that, once started, > migrations are completed within a reasonable amount of time? In the > Jenkins project, this is part of our engineering process at the design > proposal stage: > > > https://github.com/jenkinsci/jep/blob/eedd98dadbf70f69a291c9184facafc64dc82097/jep-template/0000/README.adoc?plain=1#L150-L185 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
