I missed the proposal for the version. I saw 3.2.5 and that can't be correct, hence I tried to explain what the correct version should be. So correct minimum version will be one of: 3.0, 3.1.0, 3.2.1, 3.3.1, 3.5.0 This is the version we should compile with, our integration tests use the latest bugfix for all.
Just like the discussions around what the minimum Java version should be, the same counts for the minimum Maven version. What is the benefit for version X? (Keep in mind, that every individual plugin may choose a different minimum in case a specific change/feature is required) 3.1.0 is very clear to me: switch to eclipse aether (package change) and JSR330 support for plugins. All others contain (close to) no changes to the API, so there's no real gain. By using higher versions of Maven you might force people to upgrade Maven or stick to old plugins in case they can't upgrade. I don't think it should be our plugins to enforce a higher version of Maven. Hence I don't see any reason to require 3.5.0 or 3.6.0. I think it is pretty impressive that we can say that our plugins still support a wide range of Maven versions. So my vote will be 3.1.0 Robert On 25-5-2020 22:53:47, Olivier Lamy <ol...@apache.org> wrote: @All Can we update the compatibility plan document saying we support from 3.5.4 and 3.6.3. plugins will use API from 3.5.4 and can use java8 from now (June 2020) . As 3.7.0 is on his way (soon) supporting 3 series seems enough. (with 3.7.0 using java8) @Robert As you didn't answer, I wonder if you still have strong opinions? On Sun, 24 May 2020 at 18:46, Michael Osipov wrote: > Am 2020-05-24 um 10:41 schrieb Olivier Lamy: > > On Sat, 23 May 2020 at 21:33, Robert Scholte > wrote: > > > >> As discussed before: compatibility should either be 3.3.1 (since 3.3.0 > >> didn't make it) or 3.5.0, we should not include the (highest) bugfix > >> version. > >> > > Great this means we can can rid of this hackhish refection stuff for > > aether... > > > > you mean we should support 3.3.1 3.3.3 and 3.3.9? > > by support I mean fixing security issues. > > so in this case what happen in case of a security issue for 3.3.1 do we > > have a to release 3.3.1.1 3.3.3.1 3.3.9.1 > > Not sure I understand what we mean with support? > > anyway if we say all plugins must be at least 3.3.1 it's good progress > > I think we have discussed this before as I have raised this at least > once this one. The upshot is that we try to support (in terms of API and > ABI) in Plugins and Components a huge variety of Maven versions, but > only the last stable minor branch of Maven receives fixes. > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
