Hi Benson,
This is not what I can recall.
What I do remember, but maybe that was a different discussion, is that
plugins depending on M2 classes should either be rewritten or have to
include the compat dependency themself.
Karl-Heinz is doing a great job for pushing the maven prerequisite for
plugins to M2.2.1
So far I haven't seen any complaints, but my guess it that users which
still use Maven2 were already using 2.2.1.
I'd prefer to first finish the 2.2.1 prerequisite upgrade, next get rid of
all deprecated stuff in the plugins, so they don't depend on the
Maven-compat anymore(so that is has become a real M3 plugin).
thanks,
Robert
Op Fri, 26 Sep 2014 03:19:32 +0200 schreef Benson Margulies
<bimargul...@gmail.com>:
Months ago, we had a discussion which, I believe, reached a consensus
to up the floor for components and plugins to 3.0.5. To be more
precise, to start to propagate that version for maven core
dependencies down the pom hierarchy. If someone had an itch to
maintain a branch of something that still supports 2.2.x, they are
welcome to do so.
Once the apache pom release is done, if this is still a consensus, I
propose to tee up a release of the maven pom that starts this cascade.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
