I thought you had said that it was a regression introduced in 3.0, so if prerequisites is 2.x then you should resolve the "fixed" way as that was the way of 2.x that you are *restoring*
The only reason for the bug reproduction on [3.0,3.4) is because people developing against the 3.x versions might have used hacks to work around the "bug" and hence need protection so that their "hacks" still work On Sun 1 Jan 2017 at 07:11, Christian Schulte <c...@schulte.it> wrote: > Am 01/01/17 um 08:06 schrieb Christian Schulte: > > > Am 01/01/17 um 07:52 schrieb Christian Schulte: > > >> is uncovering bugs in the poms. Current master is passing all core ITs, > > >> all plugin ITs and also can be used to build all plugins, if you > > >> manually change to a different plugin tools release > > >> (-DmavenPluginToolsVersion=3.3 or 3.5). > > > > > > It's not even needed to change the plugin tools version any more. Only > > > plugins having declared > > > > > > <prerequisites>3.4</prerequisites> > > > > > > would get the correct resolution. > > > > And all of our plugins already are working with that correct resolution > > in place but are still resolved the old way, because they declare > > prerequisites 2.0, 2.2.1 or 3.0. You can declare them prerequsisite 3.4 > > today and they'll work. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- Sent from my phone
