http://jira.codehaus.org/browse/MNG-5207
On 13 February 2014 17:15, Baptiste Mathus <m...@batmat.net> wrote: > Hi Jörg, > > multi-projects in correct order and therefore will not produce artifacts > with bogus SNAPSHOTs > > Maybe you could (re)point out the corresponding JIRAs? > > Because as a maven user, I wonder what triggers these issues for you. We > have tens of multi-projects with interdependencies being currently > developed, and I'd be interested to hear about the (problematic) use case > we don't encounter. > > > 2014-02-13 18:05 GMT+01:00 Jörg Schaible <joerg.schai...@gmx.de>: > > > Daniel Kulp wrote: > > > > > > > > On Feb 13, 2014, at 11:18 AM, Stephen Connolly > > > <stephen.alan.conno...@gmail.com> wrote: > > > > > >> I suggest you convince at least one of these people: > > >> https://people.apache.org/committers-by-project.html#maven that they > > >> should act as release manager. > > >> > > >> EOL just means we will not be making new releases, and it will be > moved > > >> to the archive section of the downloads. > > > > > > Well, one more thing: if it's officially EOL, there is a much higher > > > chance that plugins would be marked as using 3.x as a minimum and will > no > > > longer work with 2.1.1. API's and such that the plugins use will > likely > > > get updated to 3.x level. Etc.... > > > > Right. The question is already if 2.2.1 runs on Java 8 or if we have a > > compatible release plugin that allows us to switch from subversion to > git. > > With EOL of M221 those situations will grow rapidly. > > > > > Anyway, I'm +1 to dropping 2.x support. > > > > I'd switch immediately to a working 3.x version. > > > > >> You will still be able to download it. You will still be able to get > the > > >> source code. We just will be recognising the fact that there is nobody > > >> who wants to cut a release from the 2.x codebase. > > > > See above. 2.2.1 can become a dead end faster than wanted. > > > > >> Hopefully focusing on the 3.x codebase will allow us to iron out the > > bugs > > >> you feel are present in 3.x and thus preventing you from migrating... > > > > What else can we do apart from digging into Maven/Aether code ourselves? > > Providing an example project and an IT did not help to make any progress. > > > > - Jörg > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- > > Baptiste <Batmat> MATHUS - http://batmat.net > > Sauvez un arbre, > > Mangez un castor ! nbsp;! <dev-h...@maven.apache.org> > > >
