Just to refresh my memory: When working on Maven 3.4.x there were also
changes to Maven Resolver, targeted as 1.2.0.
For Maven we did a reset and pushed the version to 3.5.0.
In case as Resolver you want to have the same approach, right?
Robert
On Mon, 01 Oct 2018 12:44:38 +0200, Michael Osipov <1983-01...@gmx.net>
wrote:
You probably misunderstood. I just want to rename 1.2.0 to 1.3.0 to
avoid confusion. Nothing is lost. The target 1.2.0 was broken, therefore
we have resetted to 1.1.1 and bringing 1.2.0 back is confusing.
Gesendet: Montag, 01. Oktober 2018 um 10:43 Uhr
Von: "Robert Scholte" <apa...@sourcegrounds.com>
An: "Maven Developers List" <dev@maven.apache.org>
Betreff: Re: Skipping Resolver 1.2.0
For the FileTransformer I've already updated the version from 1.1.2 to
1.2.0 in Jira. I see no reason to push it further to 1.3.0
Robert
Verzonden vanaf mijn Samsung Galaxy-smartphone.
-------- Oorspronkelijk bericht --------Van: Michael Osipov
<micha...@apache.org> Datum: 30-09-18 22:27 (GMT+01:00) Aan: Maven
Developers List <dev@maven.apache.org> Onderwerp: Skipping Resolver
1.2.0
Folks,
I'd like to skip Resolver 1.2.0 and go straight to 1.3.0. It might lead
to confusion that we have pre-1.2.0 verions in JIRA and branch.
Any objections?
Michael
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
