On Friday, 17 August 2012, Stanislav Ochotnicky wrote: > > Quoting Stephen Connolly (2012-08-17 13:32:54) > > If in 50 years time that means that there is still some Maven plugins > that > > depend on some of the published Maven APIs from Maven 2.0 then that is a > > success on behalf of the Maven developers, not a failure to force people > to > > upgrade. > > I honestly didn't mean to make this into fail/win type scenario. > > > > In any case, you've made your opinion clear so I have a different > > > question then :-) Is there any timeframe you have in mind for this > > > transition to happen? 2 years? 5 years? 10 years? Never? I *assume* > > > there will come a time where 2.0.11 and 2.2.1 will have to die (i.e not > > > be featured as download options). I would guess the transition would > > > start at least then. > > > > > > > Apache releases never die (which is why we cannot stop people (a.k.a. > > fools) downloading Maven 2.1.0) > > I'll try to be less metaphorical next time. I meant when they will stop > to be supported by their developers. > > > > The links are there to help users that have specific requirements for > Maven > > versions, but there is absolutely nothing stopping anyone from going and > > downloading the older versions, e.g. > > http://archive.apache.org/dist/maven/binaries/ > > I am aware of archive, but having download available does not mean that > version is alive. Or should I try bugreporting against those old > versions? My guess is that those bugs would be just closed as "won't > fix". So in that sense, I believe 3.x is basically the only alive > version of Maven. 2.2.x and 2.0.x branches will likely not receive any > security or any major fixes. For you they are "done", and there's > nothing wrong with that really, but for me it means those versions have > no active upstream (pretty please take this with a grain of salt). Hence > the curiosity.
Actually there are a number of minor things to do with inter-op which may mean I spin a 2.0.12 and a 2.2.2 (specifically the metadata format change to handle resolving artifacts with classifiers) so not dead yet > > > We will probably drop the link for Maven 2.2.1 once we get to Maven 3.1 > or > > Maven 4.0 (depends on how big a change we think things are) > > > > I would suspect that a 3.1 or 4.0 might consider dropping support for JRE > > 1.5 (given that 1.6 is nearing EOL) in which case we would probably > retain > > a link to the last version that only requires JRE 1.5 such as we are > > currently doing for JRE 1.4 (i.e. the 2.0.11 link). Whether we would drop > > the 2.0.11 link at that point in time is a different question. > > OK. I can live with uncertainty and speculations. This is enough for me. > > Thank you! > > -- > Stanislav Ochotnicky <sochotni...@redhat.com <javascript:;>> > Software Engineer - Base Operating Systems Brno > > PGP: 7B087241 > Red Hat Inc. http://cz.redhat.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org <javascript:;> > For additional commands, e-mail: dev-h...@maven.apache.org <javascript:;> > >
