Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <herve.boutemy@free.fr>
To: Maven Developers List <dev@maven.apache.org>
Subject: Re: Maven resolver branch consolidation
Date: Wed, 15 Nov 2017 23:05:14 +0100
Message-ID: <7916878.yLmMccDyS7@giga>
In-Reply-To: <85c54638-d825-6c1c-a504-1388f8c777c9@apache.org>
References: <20171109053551.957D429C50D1@dd17332.kasserver.com> <1667195.t7Hg2OM9be@giga> <85c54638-d825-6c1c-a504-1388f8c777c9@apache.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
archived-at: Wed, 15 Nov 2017 22:05:20 -0000

it seems I have not been clear: I'll try to explain better

1. maven-resolver-ant-tasks depends on maven-resolver-provider (from Maven=
=20
core)
2. maven-resolver-provider (then Maven core) depends on maven-resolver

if we put maven-resolver-ant-tasks in the same reactor than maven-resolver,=
 we=20
can't release any maven-resolver API change that breaks maven-resolver-
provider

example: if we move maven-resolver code to org.apache.maven java package in=
=20
maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider 4.0.0-SNAPSH=
OT=20
that uses maven-resolver 2.0.0-SNAPSHOT with this new java package. Then tr=
y=20
to release anything: you can't, unless you don't try to release maven-
resolver-ant-tasks

(the consequence on version consistency is another way to describe the issu=
e,=20
but that is more subtle, then I chose to describe the most visible issue, w=
ith=20
API breaking change)

IMHO, another consequence could be: maven-resolver-ant-tasks would perhaps=
=20
better be versionned like maven-resolver-provider


Merging resolver-demos is really the great big idea: with that merge,=20
modifying maven-rresolver can immediately be tested with demos: that'll be =
so=20
much easier to make changes to maven-resolver code!

Regards,

Herv=E9

Le mercredi 15 novembre 2017, 09:02:12 CET Michael Osipov a =E9crit :
> Why -1 on the Ant tasks?
>=20
> Am 2017-11-15 um 00:50 schrieb Herv=E9 BOUTEMY:
> > I answered on the mailing list and on the 2 Jira issues
> > In summary, +1 to merge demos, -1 to merge ant-tasks
> >=20
> > Regards,
> >=20
> > Herv=E9
> >=20
> > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a =E9crit :
> >> Any feedback or should I just go ahead with the cleanup?
> >>=20
> >> Manfred
> >>=20
> >> Manfred Moser wrote on 2017-11-08 21:35:
> >>> Hi all,
> >>>=20
> >>> I have started and made good progress on getting Maven resolver all i=
nto
> >>> the master branch instead of having master, demos and ant-tasks in
> >>> separate branches.
> >>>=20
> >>> Details are tracked in
> >>> https://issues.apache.org/jira/browse/MRESOLVER-28
> >>>=20
> >>> All of it is now in a new branch called master-all for you to see.
> >>>=20
> >>> I am now wondering what the next steps are. I added what I think shou=
ld
> >>> happen next in the issue in a comment and would appreciate any input =
on
> >>> the current setup and next steps.
> >>>=20
> >>> Any help would be appreciated.
> >>>=20
> >>> manfred
> >>=20
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >=20
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org