You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by Manfred Moser <ma...@simpligility.com> on 2017/11/09 05:35:51 UTC

Maven resolver branch consolidation

Hi all,

I have started and made good progress on getting Maven resolver all into the master branch instead of having master, demos and ant-tasks in separate branches.

Details are tracked in https://issues.apache.org/jira/browse/MRESOLVER-28

All of it is now in a new branch called master-all for you to see.

I am now wondering what the next steps are. I added what I think should happen next in the issue in a comment and would appreciate any input on the current setup and next steps. 

Any help would be appreciated.

manfred





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

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

Hi,

I like the idea of simplification: I just factorized mavenVersion property to 
parent pom.

I have only one fear: what happens when the API changes in an incompatible way 
then we must release maven-artifact-resolver, then maven-resolver provider, 
then ant-tasks and demos.

AFAIK, this chicken and egg issue is exactly why everything was released in 3 
independent components (with associated complexity that I'd like also to 
remove)

What about creating a "withMavenProvider" module where we could put ant tasks 
and demos, which would define the mavenVersion property?
In case of such breaking change, we would just have to skip this module (and 
its sub-modules) for the API breaking release, then once the new compatible 
Maven provider is released, we could continue "the simple way"

this would give us the benefit of being simple in general, and have just 
something a little more complex in special incompatible cases.
Here, it would be "bizarre", since would bring a partial release for artifact 
resolver.

Another "bizarre effect" of this way of releasing is:
Artifact Resolver 1.1.1 will provide Ant Tasks and demos using Maven Resolver 
Provider 3.5.0, but Maven Resolver Provider 3.5.3 (or 3.6.0 or 4.0.0) will be 
the first using Artifact Resolver 1.1.1


Perhaps there is another simplification idea that would avoid this issue:
- merge demos in artifact resolver master, since demos are never really 
released
- let Ant Tasks in an independent branch (or component one day)

Regards,

Hervé

Le jeudi 9 novembre 2017, 06:35:51 CET Manfred Moser a écrit :
> Hi all,
> 
> I have started and made good progress on getting Maven resolver all into the
> master branch instead of having master, demos and ant-tasks in separate
> branches.
> 
> Details are tracked in https://issues.apache.org/jira/browse/MRESOLVER-28
> 
> All of it is now in a new branch called master-all for you to see.
> 
> I am now wondering what the next steps are. I added what I think should
> happen next in the issue in a comment and would appreciate any input on the
> current setup and next steps.
> 
> Any help would be appreciated.
> 
> manfred
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

let's start with demos: this one is really a great idea

on ant-tasks, I hope my new explanations make the issue more clear

Regards,

Hervé

Le mercredi 15 novembre 2017, 18:39:06 CET Manfred Moser a écrit :
> Sorry herve. For some reason I totally missed those. I commented on the
> issues.
> 
> In summary I would like to get the ant-tasks merged as well since that makes
> a lot more sense to me than keeping it separate.
> 
> Manfred
> 
> Hervé BOUTEMY wrote on 2017-11-14 15:50:
> > I answered on the mailing list and on the 2 Jira issues
> > In summary, +1 to merge demos, -1 to merge ant-tasks
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
> >> Any feedback or should I just go ahead with the cleanup?
> >> 
> >> Manfred
> >> 
> >> Manfred Moser wrote on 2017-11-08 21:35:
> >> > Hi all,
> >> > 
> >> > I have started and made good progress on getting Maven resolver all
> >> > into
> >> > the master branch instead of having master, demos and ant-tasks in
> >> > separate branches.
> >> > 
> >> > Details are tracked in
> >> > https://issues.apache.org/jira/browse/MRESOLVER-28
> >> > 
> >> > All of it is now in a new branch called master-all for you to see.
> >> > 
> >> > I am now wondering what the next steps are. I added what I think should
> >> > happen next in the issue in a comment and would appreciate any input on
> >> > the current setup and next steps.
> >> > 
> >> > Any help would be appreciated.
> >> > 
> >> > manfred
> >> 
> >> ---------------------------------------------------------------------
> >> 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
> 
> ---------------------------------------------------------------------
> 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

Re: Maven resolver branch consolidation

Posted by Manfred Moser <ma...@simpligility.com>.

Sorry herve. For some reason I totally missed those. I commented on the issues. 

In summary I would like to get the ant-tasks merged as well since that makes a lot more sense to me than keeping it separate. 

Manfred

Hervé BOUTEMY wrote on 2017-11-14 15:50:

> I answered on the mailing list and on the 2 Jira issues
> In summary, +1 to merge demos, -1 to merge ant-tasks
> 
> Regards,
> 
> Hervé
> 
> Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
>> Any feedback or should I just go ahead with the cleanup?
>> 
>> Manfred
>> 
>> Manfred Moser wrote on 2017-11-08 21:35:
>> > Hi all,
>> > 
>> > I have started and made good progress on getting Maven resolver all into
>> > the master branch instead of having master, demos and ant-tasks in
>> > separate branches.
>> > 
>> > Details are tracked in https://issues.apache.org/jira/browse/MRESOLVER-28
>> > 
>> > All of it is now in a new branch called master-all for you to see.
>> > 
>> > I am now wondering what the next steps are. I added what I think should
>> > happen next in the issue in a comment and would appreciate any input on
>> > the current setup and next steps.
>> > 
>> > Any help would be appreciated.
>> > 
>> > manfred
>> 
>> ---------------------------------------------------------------------
>> 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
> 


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

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

attachment removed by mailing list

I put it in
https://cwiki.apache.org/confluence/display/MAVEN/POM+Model+Version+5.0.0?
focusedCommentId=74687410&refresh=1510912447661#comment-74687410

Regards,

Hervé

Le vendredi 17 novembre 2017, 09:40:22 CET Hervé BOUTEMY a écrit :
> on the second option, I was ready to just answer "not possible", but decided
> I could try at high level before answering...
> 
> I took Maven core dependency tree [1], picked green color as the definition
> of Maven Artifact Resolver, put maven-resolver-provider in green + settings
> builder (since used by resolver ant tasks: that's a detail I didn't put in
> latest resolver dependency tree)
> Then I extended green to every transitive dependency to have an independent
> releasable reactor
> 
> You'll find as a result the attached image.
> 
> Analysis:
> - this splits Maven core in 2 parts: lower part on dependency resolution,
> higher part on build
> - settings.xml and pom.xml are in dependency resolution
> 
> Reaction: it could be for Maven 5 or 6, when consumer pom is strictly
> separate from build pom...
> 
> Regards,
> 
> Hervé
> 
> [1] http://maven.apache.org/ref/3.5.2/
> 
> Le jeudi 16 novembre 2017, 18:13:15 CET Manfred Moser a écrit :
> > Thanks for the explanation and details Herve. Seems to be that to do this
> > cleanly we have to break the circle. From my limited knowledge there are
> > two ways to do that.
> > 
> > 1. As stephen suggested.. get the resolver into maven core tree. That
> > makes
> > core bigger again and ties the two projects into one release cycle.
> > Feasible but I am not a fan.
> > 
> > 2. I am not sure if possible but .. could we get the maven resolver
> > provider out of maven core and into the resolver project and have it all
> > together in there?
> > 
> > In either case .. both of those seem rather large tasks so I will
> > definitely go ahead with demo branch merge first. I just have to redo the
> > work I did without the ant tasks in the tree. Stay tuned on that..
> > 
> > Manfred
> > 
> > Hervé BOUTEMY wrote on 2017-11-16 05:49:
> > > feasible, but I really don't like it: separation is good.
> > > 
> > > seriously, just merge demos and let ant-tasks separate, and we have a
> > > pretty good compromise on every aspect
> > > (or even drop ant tasks if really this is causing us too much
> > > headache...)
> > > 
> > > Regards,
> > > 
> > > Hervé
> > > 
> > > Le jeudi 16 novembre 2017, 10:03:07 CET Stephen Connolly a écrit :
> > >> On Thu 16 Nov 2017 at 07:51, Hervé BOUTEMY <he...@free.fr> 
wrote:
> > >> > I just pushed an update of dependencies image that shows the external
> > >> > maven-
> > >> > resolver-provider (in yellow) inside the reactor dependency graph (in
> > >> > blue)
> > >> > 
> > >> > That shows the chicken and egg issue on releasing we'll have on API
> > >> > breaking
> > >> > change. People always building from source (like Debian) will have
> > >> > the
> > >> > issue
> > >> > also.
> > >> > 
> > >> > For demos, which are not really published during the release (just as
> > >> > documentation), disabling the module in the build when necessary is
> > >> > sufficient,
> > >> > won't change many things. For ant tasks, disabling the module will
> > >> > not
> > >> > publish
> > >> > the artifact: this will have a visible impact.
> > >> 
> > >> Should we just bite the bullet and bring resolver in-tree as modules in
> > >> maven core... leaving demos and ant tasks here?
> > >> 
> > >> > Regards,
> > >> > 
> > >> > Hervé
> > >> > 
> > >> > Le mercredi 15 novembre 2017, 23:05:14 CET Hervé BOUTEMY a écrit :
> > >> > > 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
> > >> > 
> > >> > > 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 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
> > >> > 
> > >> > > maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider
> > >> > > 4.0.0-SNAPSHOT that uses maven-resolver 2.0.0-SNAPSHOT with this
> > >> > > new
> > >> > > java
> > >> > > package. Then try 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
> > >> > > issue, but that is more subtle, then I chose to describe the most
> > >> > > visible
> > >> > > issue, with API breaking change)
> > >> > > 
> > >> > > IMHO, another consequence could be: maven-resolver-ant-tasks would
> > >> > 
> > >> > perhaps
> > >> > 
> > >> > > better be versionned like maven-resolver-provider
> > >> > > 
> > >> > > 
> > >> > > Merging resolver-demos is really the great big idea: with that
> > >> > > merge,
> > >> > > modifying maven-rresolver can immediately be tested with demos:
> > >> > > that'll
> > >> > 
> > >> > be
> > >> > 
> > >> > > so much easier to make changes to maven-resolver code!
> > >> > > 
> > >> > > Regards,
> > >> > > 
> > >> > > Hervé
> > >> > > 
> > >> > > Le mercredi 15 novembre 2017, 09:02:12 CET Michael Osipov a écrit :
> > >> > > > Why -1 on the Ant tasks?
> > >> > > > 
> > >> > > > Am 2017-11-15 um 00:50 schrieb Hervé BOUTEMY:
> > >> > > > > I answered on the mailing list and on the 2 Jira issues
> > >> > > > > In summary, +1 to merge demos, -1 to merge ant-tasks
> > >> > > > > 
> > >> > > > > Regards,
> > >> > > > > 
> > >> > > > > Hervé
> > >> > > > > 
> > >> > > > > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
> > >> > > > >> Any feedback or should I just go ahead with the cleanup?
> > >> > > > >> 
> > >> > > > >> Manfred
> > >> > > > >> 
> > >> > > > >> Manfred Moser wrote on 2017-11-08 21:35:
> > >> > > > >>> Hi all,
> > >> > > > >>> 
> > >> > > > >>> I have started and made good progress on getting Maven
> > >> > > > >>> resolver
> > >> > > > >>> all
> > >> > > > >>> into
> > >> > > > >>> the master branch instead of having master, demos and
> > >> > > > >>> ant-tasks
> > >> > > > >>> in
> > >> > > > >>> separate branches.
> > >> > > > >>> 
> > >> > > > >>> Details are tracked in
> > >> > > > >>> https://issues.apache.org/jira/browse/MRESOLVER-28
> > >> > > > >>> 
> > >> > > > >>> All of it is now in a new branch called master-all for you to
> > >> > > > >>> see.
> > >> > > > >>> 
> > >> > > > >>> I am now wondering what the next steps are. I added what I
> > >> > > > >>> think
> > >> > > > >>> should
> > >> > > > >>> happen next in the issue in a comment and would appreciate
> > >> > > > >>> any
> > >> > 
> > >> > input
> > >> > 
> > >> > > > >>> on
> > >> > > > >>> the current setup and next steps.
> > >> > > > >>> 
> > >> > > > >>> Any help would be appreciated.
> > >> > > > >>> 
> > >> > > > >>> manfred
> > >> > 
> > >> > ---------------------------------------------------------------------
> > >> > 
> > >> > > > >> 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
> > >> > > 
> > >> > > -------------------------------------------------------------------
> > >> > > --
> > >> > > 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
> > >> > 
> > >> > --
> > >> 
> > >> Sent from my phone
> > > 
> > > ---------------------------------------------------------------------
> > > 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



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

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

on the second option, I was ready to just answer "not possible", but decided I 
could try at high level before answering...

I took Maven core dependency tree [1], picked green color as the definition of 
Maven Artifact Resolver, put maven-resolver-provider in green + settings 
builder (since used by resolver ant tasks: that's a detail I didn't put in 
latest resolver dependency tree)
Then I extended green to every transitive dependency to have an independent 
releasable reactor

You'll find as a result the attached image.

Analysis:
- this splits Maven core in 2 parts: lower part on dependency resolution, 
higher part on build
- settings.xml and pom.xml are in dependency resolution

Reaction: it could be for Maven 5 or 6, when consumer pom is strictly separate 
from build pom...

Regards,

Herv�

[1] http://maven.apache.org/ref/3.5.2/

Le jeudi 16 novembre 2017, 18:13:15 CET Manfred Moser a �crit :
> Thanks for the explanation and details Herve. Seems to be that to do this
> cleanly we have to break the circle. From my limited knowledge there are
> two ways to do that.
> 
> 1. As stephen suggested.. get the resolver into maven core tree. That makes
> core bigger again and ties the two projects into one release cycle.
> Feasible but I am not a fan.
> 
> 2. I am not sure if possible but .. could we get the maven resolver provider
> out of maven core and into the resolver project and have it all together in
> there?
> 
> In either case .. both of those seem rather large tasks so I will definitely
> go ahead with demo branch merge first. I just have to redo the work I did
> without the ant tasks in the tree. Stay tuned on that..
> 
> Manfred
> 
> Herv� BOUTEMY wrote on 2017-11-16 05:49:
> > feasible, but I really don't like it: separation is good.
> > 
> > seriously, just merge demos and let ant-tasks separate, and we have a
> > pretty good compromise on every aspect
> > (or even drop ant tasks if really this is causing us too much headache...)
> > 
> > Regards,
> > 
> > Herv�
> > 
> > Le jeudi 16 novembre 2017, 10:03:07 CET Stephen Connolly a �crit :
> >> On Thu 16 Nov 2017 at 07:51, Herv� BOUTEMY <he...@free.fr> wrote:
> >> > I just pushed an update of dependencies image that shows the external
> >> > maven-
> >> > resolver-provider (in yellow) inside the reactor dependency graph (in
> >> > blue)
> >> > 
> >> > That shows the chicken and egg issue on releasing we'll have on API
> >> > breaking
> >> > change. People always building from source (like Debian) will have the
> >> > issue
> >> > also.
> >> > 
> >> > For demos, which are not really published during the release (just as
> >> > documentation), disabling the module in the build when necessary is
> >> > sufficient,
> >> > won't change many things. For ant tasks, disabling the module will not
> >> > publish
> >> > the artifact: this will have a visible impact.
> >> 
> >> Should we just bite the bullet and bring resolver in-tree as modules in
> >> maven core... leaving demos and ant tasks here?
> >> 
> >> > Regards,
> >> > 
> >> > Herv�
> >> > 
> >> > Le mercredi 15 novembre 2017, 23:05:14 CET Herv� BOUTEMY a �crit :
> >> > > 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
> >> > 
> >> > > 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 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
> >> > 
> >> > > maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider
> >> > > 4.0.0-SNAPSHOT that uses maven-resolver 2.0.0-SNAPSHOT with this new
> >> > > java
> >> > > package. Then try 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
> >> > > issue, but that is more subtle, then I chose to describe the most
> >> > > visible
> >> > > issue, with API breaking change)
> >> > > 
> >> > > IMHO, another consequence could be: maven-resolver-ant-tasks would
> >> > 
> >> > perhaps
> >> > 
> >> > > better be versionned like maven-resolver-provider
> >> > > 
> >> > > 
> >> > > Merging resolver-demos is really the great big idea: with that merge,
> >> > > modifying maven-rresolver can immediately be tested with demos:
> >> > > that'll
> >> > 
> >> > be
> >> > 
> >> > > so much easier to make changes to maven-resolver code!
> >> > > 
> >> > > Regards,
> >> > > 
> >> > > Herv�
> >> > > 
> >> > > Le mercredi 15 novembre 2017, 09:02:12 CET Michael Osipov a �crit :
> >> > > > Why -1 on the Ant tasks?
> >> > > > 
> >> > > > Am 2017-11-15 um 00:50 schrieb Herv� BOUTEMY:
> >> > > > > I answered on the mailing list and on the 2 Jira issues
> >> > > > > In summary, +1 to merge demos, -1 to merge ant-tasks
> >> > > > > 
> >> > > > > Regards,
> >> > > > > 
> >> > > > > Herv�
> >> > > > > 
> >> > > > > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a �crit :
> >> > > > >> Any feedback or should I just go ahead with the cleanup?
> >> > > > >> 
> >> > > > >> Manfred
> >> > > > >> 
> >> > > > >> Manfred Moser wrote on 2017-11-08 21:35:
> >> > > > >>> Hi all,
> >> > > > >>> 
> >> > > > >>> I have started and made good progress on getting Maven resolver
> >> > > > >>> all
> >> > > > >>> into
> >> > > > >>> the master branch instead of having master, demos and ant-tasks
> >> > > > >>> in
> >> > > > >>> separate branches.
> >> > > > >>> 
> >> > > > >>> Details are tracked in
> >> > > > >>> https://issues.apache.org/jira/browse/MRESOLVER-28
> >> > > > >>> 
> >> > > > >>> All of it is now in a new branch called master-all for you to
> >> > > > >>> see.
> >> > > > >>> 
> >> > > > >>> I am now wondering what the next steps are. I added what I
> >> > > > >>> think
> >> > > > >>> should
> >> > > > >>> happen next in the issue in a comment and would appreciate any
> >> > 
> >> > input
> >> > 
> >> > > > >>> on
> >> > > > >>> the current setup and next steps.
> >> > > > >>> 
> >> > > > >>> Any help would be appreciated.
> >> > > > >>> 
> >> > > > >>> manfred
> >> > 
> >> > ---------------------------------------------------------------------
> >> > 
> >> > > > >> 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
> >> > > 
> >> > > ---------------------------------------------------------------------
> >> > > 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
> >> > 
> >> > --
> >> 
> >> Sent from my phone
> > 
> > ---------------------------------------------------------------------
> > 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

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

this won't work: you'll be able to fool the compiler, but not maven-shade-
plugin when it builds the full jar with runtime dependencies

Regards,

Hervé

Le vendredi 17 novembre 2017, 12:10:49 CET Robert Scholte a écrit :
> "We can solve any problem by introducing an extra level of indirection."
> [1]
> 
> Looking at this new image[1] it is weird to me that ant-tasks has a direct
> dependency on maven-resolver-provider. I would have expected some provider
> abstraction where you can choose to use the maven-resolver-provider.
> 
> Merging it into one project is an interesting option, but I think the
> maven-artifact-resolver is isolated enough to deserve its own project.
> 
> thanks,
> Robert
> 
> [1]
> https://en.wikipedia.org/wiki/Fundamental_theorem_of_software_engineering
> [2]
> https://git1-us-west.apache.org/repos/asf?p=maven-resolver.git;a=blob_plain;
> f=src/site/resources/images/maven-resolver-deps.png;hb=f5439fde
> 
> On Thu, 16 Nov 2017 18:13:15 +0100, Manfred Moser
> 
> <ma...@simpligility.com> wrote:
> > Thanks for the explanation and details Herve. Seems to be that to do
> > this cleanly we have to break the circle. From my limited knowledge
> > there are two ways to do that.
> > 
> > 1. As stephen suggested.. get the resolver into maven core tree. That
> > makes core bigger again and ties the two projects into one release
> > cycle. Feasible but I am not a fan.
> > 
> > 2. I am not sure if possible but .. could we get the maven resolver
> > provider out of maven core and into the resolver project and have it all
> > together in there?
> > 
> > In either case .. both of those seem rather large tasks so I will
> > definitely go ahead with demo branch merge first. I just have to redo
> > the work I did without the ant tasks in the tree. Stay tuned on that..
> > 
> > Manfred
> > 
> > Hervé BOUTEMY wrote on 2017-11-16 05:49:
> >> feasible, but I really don't like it: separation is good.
> >> 
> >> seriously, just merge demos and let ant-tasks separate, and we have a
> >> pretty
> >> good compromise on every aspect
> >> (or even drop ant tasks if really this is causing us too much
> >> headache...)
> >> 
> >> Regards,
> >> 
> >> Hervé
> >> 
> >> Le jeudi 16 novembre 2017, 10:03:07 CET Stephen Connolly a écrit :
> >>> On Thu 16 Nov 2017 at 07:51, Hervé BOUTEMY <he...@free.fr>
> >>> 
> >>> wrote:
> >>> > I just pushed an update of dependencies image that shows the external
> >>> > maven-
> >>> > resolver-provider (in yellow) inside the reactor dependency graph (in
> >>> > blue)
> >>> > 
> >>> > That shows the chicken and egg issue on releasing we'll have on API
> >>> > breaking
> >>> > change. People always building from source (like Debian) will have
> >>> 
> >>> the
> >>> 
> >>> > issue
> >>> > also.
> >>> > 
> >>> > For demos, which are not really published during the release (just as
> >>> > documentation), disabling the module in the build when necessary is
> >>> > sufficient,
> >>> > won't change many things. For ant tasks, disabling the module will
> >>> 
> >>> not
> >>> 
> >>> > publish
> >>> > the artifact: this will have a visible impact.
> >>> 
> >>> Should we just bite the bullet and bring resolver in-tree as modules in
> >>> maven core... leaving demos and ant tasks here?
> >>> 
> >>> > Regards,
> >>> > 
> >>> > Hervé
> >>> > 
> >>> > Le mercredi 15 novembre 2017, 23:05:14 CET Hervé BOUTEMY a écrit :
> >>> > > 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
> >>> > 
> >>> > > 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 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
> >>> > 
> >>> > > maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider
> >>> > > 4.0.0-SNAPSHOT that uses maven-resolver 2.0.0-SNAPSHOT with this
> >>> 
> >>> new
> >>> 
> >>> > > java
> >>> > > package. Then try 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
> >>> 
> >>> > > issue, but that is more subtle, then I chose to describe the most
> >>> > > visible
> >>> > > issue, with API breaking change)
> >>> > > 
> >>> > > IMHO, another consequence could be: maven-resolver-ant-tasks would
> >>> > 
> >>> > perhaps
> >>> > 
> >>> > > better be versionned like maven-resolver-provider
> >>> > > 
> >>> > > 
> >>> > > Merging resolver-demos is really the great big idea: with that
> >>> 
> >>> merge,
> >>> 
> >>> > > modifying maven-rresolver can immediately be tested with demos:
> >>> that'll
> >>> 
> >>> > be
> >>> > 
> >>> > > so much easier to make changes to maven-resolver code!
> >>> > > 
> >>> > > Regards,
> >>> > > 
> >>> > > Hervé
> >>> > > 
> >>> > > Le mercredi 15 novembre 2017, 09:02:12 CET Michael Osipov a écrit :
> >>> > > > Why -1 on the Ant tasks?
> >>> > > > 
> >>> > > > Am 2017-11-15 um 00:50 schrieb Hervé BOUTEMY:
> >>> > > > > I answered on the mailing list and on the 2 Jira issues
> >>> > > > > In summary, +1 to merge demos, -1 to merge ant-tasks
> >>> > > > > 
> >>> > > > > Regards,
> >>> > > > > 
> >>> > > > > Hervé
> >>> > > > > 
> >>> > > > > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
> >>> > > > >> Any feedback or should I just go ahead with the cleanup?
> >>> > > > >> 
> >>> > > > >> Manfred
> >>> > > > >> 
> >>> > > > >> Manfred Moser wrote on 2017-11-08 21:35:
> >>> > > > >>> Hi all,
> >>> > > > >>> 
> >>> > > > >>> I have started and made good progress on getting Maven
> >>> 
> >>> resolver
> >>> 
> >>> > > > >>> all
> >>> > > > >>> into
> >>> > > > >>> the master branch instead of having master, demos and
> >>> 
> >>> ant-tasks in
> >>> 
> >>> > > > >>> separate branches.
> >>> > > > >>> 
> >>> > > > >>> Details are tracked in
> >>> > > > >>> https://issues.apache.org/jira/browse/MRESOLVER-28
> >>> > > > >>> 
> >>> > > > >>> All of it is now in a new branch called master-all for you
> >>> 
> >>> to see.
> >>> 
> >>> > > > >>> I am now wondering what the next steps are. I added what I
> >>> 
> >>> think
> >>> 
> >>> > > > >>> should
> >>> > > > >>> happen next in the issue in a comment and would appreciate
> >>> 
> >>> any
> >>> 
> >>> > input
> >>> > 
> >>> > > > >>> on
> >>> > > > >>> the current setup and next steps.
> >>> > > > >>> 
> >>> > > > >>> Any help would be appreciated.
> >>> > > > >>> 
> >>> > > > >>> manfred
> >>> > 
> >>> > ---------------------------------------------------------------------
> >>> > 
> >>> > > > >> 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
> >>> 
> >>> ---------------------------------------------------------------------
> >>> 
> >>> > > 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
> >>> > 
> >>> > --
> >>> 
> >>> Sent from my phone
> >> 
> >> ---------------------------------------------------------------------
> >> 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
> 
> ---------------------------------------------------------------------
> 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

Re: Maven resolver branch consolidation

Posted by Manfred Moser <ma...@simpligility.com>.

Hahah ... what a pain. Since so at this stage I think I will move the demos into the master and leave the ant tasks as they stand and 
close the relevant tickets with remarks that details this situation.

Manfred

Robert Scholte wrote on 2017-11-17 03:10:

> "We can solve any problem by introducing an extra level of indirection."  
> [1]
> 
> Looking at this new image[1] it is weird to me that ant-tasks has a direct  
> dependency on maven-resolver-provider. I would have expected some provider  
> abstraction where you can choose to use the maven-resolver-provider.
> 
> Merging it into one project is an interesting option, but I think the  
> maven-artifact-resolver is isolated enough to deserve its own project.
> 
> thanks,
> Robert
> 
> [1]  
> https://en.wikipedia.org/wiki/Fundamental_theorem_of_software_engineering
> [2]  
> https://git1-us-west.apache.org/repos/asf?p=maven-resolver.git;a=blob_plain;f=src/site/resources/images/maven-resolver-deps.png;hb=f5439fde
> 
> On Thu, 16 Nov 2017 18:13:15 +0100, Manfred Moser  
> <ma...@simpligility.com> wrote:
> 
>> Thanks for the explanation and details Herve. Seems to be that to do  
>> this cleanly we have to break the circle. From my limited knowledge  
>> there are two ways to do that.
>>
>> 1. As stephen suggested.. get the resolver into maven core tree. That  
>> makes core bigger again and ties the two projects into one release  
>> cycle. Feasible but I am not a fan.
>>
>> 2. I am not sure if possible but .. could we get the maven resolver  
>> provider out of maven core and into the resolver project and have it all  
>> together in there?
>>
>> In either case .. both of those seem rather large tasks so I will  
>> definitely go ahead with demo branch merge first. I just have to redo  
>> the work I did without the ant tasks in the tree. Stay tuned on that..
>>
>> Manfred
>>
>> Hervé BOUTEMY wrote on 2017-11-16 05:49:
>>
>>> feasible, but I really don't like it: separation is good.
>>>
>>> seriously, just merge demos and let ant-tasks separate, and we have a  
>>> pretty
>>> good compromise on every aspect
>>> (or even drop ant tasks if really this is causing us too much  
>>> headache...)
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> Le jeudi 16 novembre 2017, 10:03:07 CET Stephen Connolly a écrit :
>>>> On Thu 16 Nov 2017 at 07:51, Hervé BOUTEMY <he...@free.fr>  
>>>> wrote:
>>>> > I just pushed an update of dependencies image that shows the external
>>>> > maven-
>>>> > resolver-provider (in yellow) inside the reactor dependency graph (in
>>>> > blue)
>>>> >
>>>> > That shows the chicken and egg issue on releasing we'll have on API
>>>> > breaking
>>>> > change. People always building from source (like Debian) will have  
>>>> the
>>>> > issue
>>>> > also.
>>>> >
>>>> > For demos, which are not really published during the release (just as
>>>> > documentation), disabling the module in the build when necessary is
>>>> > sufficient,
>>>> > won't change many things. For ant tasks, disabling the module will  
>>>> not
>>>> > publish
>>>> > the artifact: this will have a visible impact.
>>>>
>>>> Should we just bite the bullet and bring resolver in-tree as modules in
>>>> maven core... leaving demos and ant tasks here?
>>>>
>>>> > Regards,
>>>> >
>>>> > Hervé
>>>> >
>>>> > Le mercredi 15 novembre 2017, 23:05:14 CET Hervé BOUTEMY a écrit :
>>>> > > 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
>>>> >
>>>> > > 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 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
>>>> >
>>>> > > maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider
>>>> > > 4.0.0-SNAPSHOT that uses maven-resolver 2.0.0-SNAPSHOT with this  
>>>> new
>>>> > > java
>>>> > > package. Then try 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
>>>> > > issue, but that is more subtle, then I chose to describe the most
>>>> > > visible
>>>> > > issue, with API breaking change)
>>>> > >
>>>> > > IMHO, another consequence could be: maven-resolver-ant-tasks would
>>>> >
>>>> > perhaps
>>>> >
>>>> > > better be versionned like maven-resolver-provider
>>>> > >
>>>> > >
>>>> > > Merging resolver-demos is really the great big idea: with that  
>>>> merge,
>>>> > > modifying maven-rresolver can immediately be tested with demos:  
>>>> that'll
>>>> >
>>>> > be
>>>> >
>>>> > > so much easier to make changes to maven-resolver code!
>>>> > >
>>>> > > Regards,
>>>> > >
>>>> > > Hervé
>>>> > >
>>>> > > Le mercredi 15 novembre 2017, 09:02:12 CET Michael Osipov a écrit :
>>>> > > > Why -1 on the Ant tasks?
>>>> > > >
>>>> > > > Am 2017-11-15 um 00:50 schrieb Hervé BOUTEMY:
>>>> > > > > I answered on the mailing list and on the 2 Jira issues
>>>> > > > > In summary, +1 to merge demos, -1 to merge ant-tasks
>>>> > > > >
>>>> > > > > Regards,
>>>> > > > >
>>>> > > > > Hervé
>>>> > > > >
>>>> > > > > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
>>>> > > > >> Any feedback or should I just go ahead with the cleanup?
>>>> > > > >>
>>>> > > > >> Manfred
>>>> > > > >>
>>>> > > > >> Manfred Moser wrote on 2017-11-08 21:35:
>>>> > > > >>> Hi all,
>>>> > > > >>>
>>>> > > > >>> I have started and made good progress on getting Maven  
>>>> resolver
>>>> > > > >>> all
>>>> > > > >>> into
>>>> > > > >>> the master branch instead of having master, demos and  
>>>> ant-tasks in
>>>> > > > >>> separate branches.
>>>> > > > >>>
>>>> > > > >>> Details are tracked in
>>>> > > > >>> https://issues.apache.org/jira/browse/MRESOLVER-28
>>>> > > > >>>
>>>> > > > >>> All of it is now in a new branch called master-all for you  
>>>> to see.
>>>> > > > >>>
>>>> > > > >>> I am now wondering what the next steps are. I added what I  
>>>> think
>>>> > > > >>> should
>>>> > > > >>> happen next in the issue in a comment and would appreciate  
>>>> any
>>>> >
>>>> > input
>>>> >
>>>> > > > >>> on
>>>> > > > >>> the current setup and next steps.
>>>> > > > >>>
>>>> > > > >>> Any help would be appreciated.
>>>> > > > >>>
>>>> > > > >>> manfred
>>>> >
>>>> > ---------------------------------------------------------------------
>>>> >
>>>> > > > >> 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
>>>> > >
>>>> > >  
>>>> ---------------------------------------------------------------------
>>>> > > 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
>>>> >
>>>> > --
>>>>
>>>> Sent from my phone
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
> 
> ---------------------------------------------------------------------
> 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

Re: Maven resolver branch consolidation

Posted by Robert Scholte <rf...@apache.org>.

"We can solve any problem by introducing an extra level of indirection."  
[1]

Looking at this new image[1] it is weird to me that ant-tasks has a direct  
dependency on maven-resolver-provider. I would have expected some provider  
abstraction where you can choose to use the maven-resolver-provider.

Merging it into one project is an interesting option, but I think the  
maven-artifact-resolver is isolated enough to deserve its own project.

thanks,
Robert

[1]  
https://en.wikipedia.org/wiki/Fundamental_theorem_of_software_engineering
[2]  
https://git1-us-west.apache.org/repos/asf?p=maven-resolver.git;a=blob_plain;f=src/site/resources/images/maven-resolver-deps.png;hb=f5439fde

On Thu, 16 Nov 2017 18:13:15 +0100, Manfred Moser  
<ma...@simpligility.com> wrote:

> Thanks for the explanation and details Herve. Seems to be that to do  
> this cleanly we have to break the circle. From my limited knowledge  
> there are two ways to do that.
>
> 1. As stephen suggested.. get the resolver into maven core tree. That  
> makes core bigger again and ties the two projects into one release  
> cycle. Feasible but I am not a fan.
>
> 2. I am not sure if possible but .. could we get the maven resolver  
> provider out of maven core and into the resolver project and have it all  
> together in there?
>
> In either case .. both of those seem rather large tasks so I will  
> definitely go ahead with demo branch merge first. I just have to redo  
> the work I did without the ant tasks in the tree. Stay tuned on that..
>
> Manfred
>
> Hervé BOUTEMY wrote on 2017-11-16 05:49:
>
>> feasible, but I really don't like it: separation is good.
>>
>> seriously, just merge demos and let ant-tasks separate, and we have a  
>> pretty
>> good compromise on every aspect
>> (or even drop ant tasks if really this is causing us too much  
>> headache...)
>>
>> Regards,
>>
>> Hervé
>>
>> Le jeudi 16 novembre 2017, 10:03:07 CET Stephen Connolly a écrit :
>>> On Thu 16 Nov 2017 at 07:51, Hervé BOUTEMY <he...@free.fr>  
>>> wrote:
>>> > I just pushed an update of dependencies image that shows the external
>>> > maven-
>>> > resolver-provider (in yellow) inside the reactor dependency graph (in
>>> > blue)
>>> >
>>> > That shows the chicken and egg issue on releasing we'll have on API
>>> > breaking
>>> > change. People always building from source (like Debian) will have  
>>> the
>>> > issue
>>> > also.
>>> >
>>> > For demos, which are not really published during the release (just as
>>> > documentation), disabling the module in the build when necessary is
>>> > sufficient,
>>> > won't change many things. For ant tasks, disabling the module will  
>>> not
>>> > publish
>>> > the artifact: this will have a visible impact.
>>>
>>> Should we just bite the bullet and bring resolver in-tree as modules in
>>> maven core... leaving demos and ant tasks here?
>>>
>>> > Regards,
>>> >
>>> > Hervé
>>> >
>>> > Le mercredi 15 novembre 2017, 23:05:14 CET Hervé BOUTEMY a écrit :
>>> > > 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
>>> >
>>> > > 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 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
>>> >
>>> > > maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider
>>> > > 4.0.0-SNAPSHOT that uses maven-resolver 2.0.0-SNAPSHOT with this  
>>> new
>>> > > java
>>> > > package. Then try 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
>>> > > issue, but that is more subtle, then I chose to describe the most
>>> > > visible
>>> > > issue, with API breaking change)
>>> > >
>>> > > IMHO, another consequence could be: maven-resolver-ant-tasks would
>>> >
>>> > perhaps
>>> >
>>> > > better be versionned like maven-resolver-provider
>>> > >
>>> > >
>>> > > Merging resolver-demos is really the great big idea: with that  
>>> merge,
>>> > > modifying maven-rresolver can immediately be tested with demos:  
>>> that'll
>>> >
>>> > be
>>> >
>>> > > so much easier to make changes to maven-resolver code!
>>> > >
>>> > > Regards,
>>> > >
>>> > > Hervé
>>> > >
>>> > > Le mercredi 15 novembre 2017, 09:02:12 CET Michael Osipov a écrit :
>>> > > > Why -1 on the Ant tasks?
>>> > > >
>>> > > > Am 2017-11-15 um 00:50 schrieb Hervé BOUTEMY:
>>> > > > > I answered on the mailing list and on the 2 Jira issues
>>> > > > > In summary, +1 to merge demos, -1 to merge ant-tasks
>>> > > > >
>>> > > > > Regards,
>>> > > > >
>>> > > > > Hervé
>>> > > > >
>>> > > > > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
>>> > > > >> Any feedback or should I just go ahead with the cleanup?
>>> > > > >>
>>> > > > >> Manfred
>>> > > > >>
>>> > > > >> Manfred Moser wrote on 2017-11-08 21:35:
>>> > > > >>> Hi all,
>>> > > > >>>
>>> > > > >>> I have started and made good progress on getting Maven  
>>> resolver
>>> > > > >>> all
>>> > > > >>> into
>>> > > > >>> the master branch instead of having master, demos and  
>>> ant-tasks in
>>> > > > >>> separate branches.
>>> > > > >>>
>>> > > > >>> Details are tracked in
>>> > > > >>> https://issues.apache.org/jira/browse/MRESOLVER-28
>>> > > > >>>
>>> > > > >>> All of it is now in a new branch called master-all for you  
>>> to see.
>>> > > > >>>
>>> > > > >>> I am now wondering what the next steps are. I added what I  
>>> think
>>> > > > >>> should
>>> > > > >>> happen next in the issue in a comment and would appreciate  
>>> any
>>> >
>>> > input
>>> >
>>> > > > >>> on
>>> > > > >>> the current setup and next steps.
>>> > > > >>>
>>> > > > >>> Any help would be appreciated.
>>> > > > >>>
>>> > > > >>> manfred
>>> >
>>> > ---------------------------------------------------------------------
>>> >
>>> > > > >> 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
>>> > >
>>> > >  
>>> ---------------------------------------------------------------------
>>> > > 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
>>> >
>>> > --
>>>
>>> Sent from my phone
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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

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

Re: Maven resolver branch consolidation

Posted by Manfred Moser <ma...@simpligility.com>.

Thanks for the explanation and details Herve. Seems to be that to do this cleanly we have to break the circle. From my limited knowledge there are two ways to do that.

1. As stephen suggested.. get the resolver into maven core tree. That makes core bigger again and ties the two projects into one release cycle. Feasible but I am not a fan.

2. I am not sure if possible but .. could we get the maven resolver provider out of maven core and into the resolver project and have it all together in there?

In either case .. both of those seem rather large tasks so I will definitely go ahead with demo branch merge first. I just have to redo the work I did without the ant tasks in the tree. Stay tuned on that.. 

Manfred

Hervé BOUTEMY wrote on 2017-11-16 05:49:

> feasible, but I really don't like it: separation is good.
> 
> seriously, just merge demos and let ant-tasks separate, and we have a pretty 
> good compromise on every aspect
> (or even drop ant tasks if really this is causing us too much headache...)
> 
> Regards,
> 
> Hervé
> 
> Le jeudi 16 novembre 2017, 10:03:07 CET Stephen Connolly a écrit :
>> On Thu 16 Nov 2017 at 07:51, Hervé BOUTEMY <he...@free.fr> wrote:
>> > I just pushed an update of dependencies image that shows the external
>> > maven-
>> > resolver-provider (in yellow) inside the reactor dependency graph (in
>> > blue)
>> > 
>> > That shows the chicken and egg issue on releasing we'll have on API
>> > breaking
>> > change. People always building from source (like Debian) will have the
>> > issue
>> > also.
>> > 
>> > For demos, which are not really published during the release (just as
>> > documentation), disabling the module in the build when necessary is
>> > sufficient,
>> > won't change many things. For ant tasks, disabling the module will not
>> > publish
>> > the artifact: this will have a visible impact.
>> 
>> Should we just bite the bullet and bring resolver in-tree as modules in
>> maven core... leaving demos and ant tasks here?
>> 
>> > Regards,
>> > 
>> > Hervé
>> > 
>> > Le mercredi 15 novembre 2017, 23:05:14 CET Hervé BOUTEMY a écrit :
>> > > 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
>> > 
>> > > 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 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
>> > 
>> > > maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider
>> > > 4.0.0-SNAPSHOT that uses maven-resolver 2.0.0-SNAPSHOT with this new
>> > > java
>> > > package. Then try 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
>> > > issue, but that is more subtle, then I chose to describe the most
>> > > visible
>> > > issue, with API breaking change)
>> > > 
>> > > IMHO, another consequence could be: maven-resolver-ant-tasks would
>> > 
>> > perhaps
>> > 
>> > > better be versionned like maven-resolver-provider
>> > > 
>> > > 
>> > > Merging resolver-demos is really the great big idea: with that merge,
>> > > modifying maven-rresolver can immediately be tested with demos: that'll
>> > 
>> > be
>> > 
>> > > so much easier to make changes to maven-resolver code!
>> > > 
>> > > Regards,
>> > > 
>> > > Hervé
>> > > 
>> > > Le mercredi 15 novembre 2017, 09:02:12 CET Michael Osipov a écrit :
>> > > > Why -1 on the Ant tasks?
>> > > > 
>> > > > Am 2017-11-15 um 00:50 schrieb Hervé BOUTEMY:
>> > > > > I answered on the mailing list and on the 2 Jira issues
>> > > > > In summary, +1 to merge demos, -1 to merge ant-tasks
>> > > > > 
>> > > > > Regards,
>> > > > > 
>> > > > > Hervé
>> > > > > 
>> > > > > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
>> > > > >> Any feedback or should I just go ahead with the cleanup?
>> > > > >> 
>> > > > >> Manfred
>> > > > >> 
>> > > > >> Manfred Moser wrote on 2017-11-08 21:35:
>> > > > >>> Hi all,
>> > > > >>> 
>> > > > >>> I have started and made good progress on getting Maven resolver
>> > > > >>> all
>> > > > >>> into
>> > > > >>> the master branch instead of having master, demos and ant-tasks in
>> > > > >>> separate branches.
>> > > > >>> 
>> > > > >>> Details are tracked in
>> > > > >>> https://issues.apache.org/jira/browse/MRESOLVER-28
>> > > > >>> 
>> > > > >>> All of it is now in a new branch called master-all for you to see.
>> > > > >>> 
>> > > > >>> I am now wondering what the next steps are. I added what I think
>> > > > >>> should
>> > > > >>> happen next in the issue in a comment and would appreciate any
>> > 
>> > input
>> > 
>> > > > >>> on
>> > > > >>> the current setup and next steps.
>> > > > >>> 
>> > > > >>> Any help would be appreciated.
>> > > > >>> 
>> > > > >>> manfred
>> > 
>> > ---------------------------------------------------------------------
>> > 
>> > > > >> 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
>> > > 
>> > > ---------------------------------------------------------------------
>> > > 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
>> > 
>> > --
>> 
>> Sent from my phone
> 
> 
> 
> ---------------------------------------------------------------------
> 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

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

feasible, but I really don't like it: separation is good.

seriously, just merge demos and let ant-tasks separate, and we have a pretty 
good compromise on every aspect
(or even drop ant tasks if really this is causing us too much headache...)

Regards,

Hervé

Le jeudi 16 novembre 2017, 10:03:07 CET Stephen Connolly a écrit :
> On Thu 16 Nov 2017 at 07:51, Hervé BOUTEMY <he...@free.fr> wrote:
> > I just pushed an update of dependencies image that shows the external
> > maven-
> > resolver-provider (in yellow) inside the reactor dependency graph (in
> > blue)
> > 
> > That shows the chicken and egg issue on releasing we'll have on API
> > breaking
> > change. People always building from source (like Debian) will have the
> > issue
> > also.
> > 
> > For demos, which are not really published during the release (just as
> > documentation), disabling the module in the build when necessary is
> > sufficient,
> > won't change many things. For ant tasks, disabling the module will not
> > publish
> > the artifact: this will have a visible impact.
> 
> Should we just bite the bullet and bring resolver in-tree as modules in
> maven core... leaving demos and ant tasks here?
> 
> > Regards,
> > 
> > Hervé
> > 
> > Le mercredi 15 novembre 2017, 23:05:14 CET Hervé BOUTEMY a écrit :
> > > 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
> > 
> > > 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 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
> > 
> > > maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider
> > > 4.0.0-SNAPSHOT that uses maven-resolver 2.0.0-SNAPSHOT with this new
> > > java
> > > package. Then try 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
> > > issue, but that is more subtle, then I chose to describe the most
> > > visible
> > > issue, with API breaking change)
> > > 
> > > IMHO, another consequence could be: maven-resolver-ant-tasks would
> > 
> > perhaps
> > 
> > > better be versionned like maven-resolver-provider
> > > 
> > > 
> > > Merging resolver-demos is really the great big idea: with that merge,
> > > modifying maven-rresolver can immediately be tested with demos: that'll
> > 
> > be
> > 
> > > so much easier to make changes to maven-resolver code!
> > > 
> > > Regards,
> > > 
> > > Hervé
> > > 
> > > Le mercredi 15 novembre 2017, 09:02:12 CET Michael Osipov a écrit :
> > > > Why -1 on the Ant tasks?
> > > > 
> > > > Am 2017-11-15 um 00:50 schrieb Hervé BOUTEMY:
> > > > > I answered on the mailing list and on the 2 Jira issues
> > > > > In summary, +1 to merge demos, -1 to merge ant-tasks
> > > > > 
> > > > > Regards,
> > > > > 
> > > > > Hervé
> > > > > 
> > > > > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
> > > > >> Any feedback or should I just go ahead with the cleanup?
> > > > >> 
> > > > >> Manfred
> > > > >> 
> > > > >> Manfred Moser wrote on 2017-11-08 21:35:
> > > > >>> Hi all,
> > > > >>> 
> > > > >>> I have started and made good progress on getting Maven resolver
> > > > >>> all
> > > > >>> into
> > > > >>> the master branch instead of having master, demos and ant-tasks in
> > > > >>> separate branches.
> > > > >>> 
> > > > >>> Details are tracked in
> > > > >>> https://issues.apache.org/jira/browse/MRESOLVER-28
> > > > >>> 
> > > > >>> All of it is now in a new branch called master-all for you to see.
> > > > >>> 
> > > > >>> I am now wondering what the next steps are. I added what I think
> > > > >>> should
> > > > >>> happen next in the issue in a comment and would appreciate any
> > 
> > input
> > 
> > > > >>> on
> > > > >>> the current setup and next steps.
> > > > >>> 
> > > > >>> Any help would be appreciated.
> > > > >>> 
> > > > >>> manfred
> > 
> > ---------------------------------------------------------------------
> > 
> > > > >> 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
> > > 
> > > ---------------------------------------------------------------------
> > > 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
> > 
> > --
> 
> Sent from my phone



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

Re: Maven resolver branch consolidation

Posted by Stephen Connolly <st...@gmail.com>.

On Thu 16 Nov 2017 at 07:51, Hervé BOUTEMY <he...@free.fr> wrote:

> I just pushed an update of dependencies image that shows the external
> maven-
> resolver-provider (in yellow) inside the reactor dependency graph (in blue)
>
> That shows the chicken and egg issue on releasing we'll have on API
> breaking
> change. People always building from source (like Debian) will have the
> issue
> also.
>
> For demos, which are not really published during the release (just as
> documentation), disabling the module in the build when necessary is
> sufficient,
> won't change many things. For ant tasks, disabling the module will not
> publish
> the artifact: this will have a visible impact.


Should we just bite the bullet and bring resolver in-tree as modules in
maven core... leaving demos and ant tasks here?


>
> Regards,
>
> Hervé
>
> Le mercredi 15 novembre 2017, 23:05:14 CET Hervé BOUTEMY a écrit :
> > 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
> > 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 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
> > maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider
> > 4.0.0-SNAPSHOT that uses maven-resolver 2.0.0-SNAPSHOT with this new java
> > package. Then try 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
> > issue, but that is more subtle, then I chose to describe the most visible
> > issue, with API breaking change)
> >
> > IMHO, another consequence could be: maven-resolver-ant-tasks would
> perhaps
> > better be versionned like maven-resolver-provider
> >
> >
> > Merging resolver-demos is really the great big idea: with that merge,
> > modifying maven-rresolver can immediately be tested with demos: that'll
> be
> > so much easier to make changes to maven-resolver code!
> >
> > Regards,
> >
> > Hervé
> >
> > Le mercredi 15 novembre 2017, 09:02:12 CET Michael Osipov a écrit :
> > > Why -1 on the Ant tasks?
> > >
> > > Am 2017-11-15 um 00:50 schrieb Hervé BOUTEMY:
> > > > I answered on the mailing list and on the 2 Jira issues
> > > > In summary, +1 to merge demos, -1 to merge ant-tasks
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
> > > >> Any feedback or should I just go ahead with the cleanup?
> > > >>
> > > >> Manfred
> > > >>
> > > >> Manfred Moser wrote on 2017-11-08 21:35:
> > > >>> Hi all,
> > > >>>
> > > >>> I have started and made good progress on getting Maven resolver all
> > > >>> into
> > > >>> the master branch instead of having master, demos and ant-tasks in
> > > >>> separate branches.
> > > >>>
> > > >>> Details are tracked in
> > > >>> https://issues.apache.org/jira/browse/MRESOLVER-28
> > > >>>
> > > >>> All of it is now in a new branch called master-all for you to see.
> > > >>>
> > > >>> I am now wondering what the next steps are. I added what I think
> > > >>> should
> > > >>> happen next in the issue in a comment and would appreciate any
> input
> > > >>> on
> > > >>> the current setup and next steps.
> > > >>>
> > > >>> Any help would be appreciated.
> > > >>>
> > > >>> manfred
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> 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
> >
> > ---------------------------------------------------------------------
> > 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
>
> --
Sent from my phone

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

I just pushed an update of dependencies image that shows the external maven-
resolver-provider (in yellow) inside the reactor dependency graph (in blue)

That shows the chicken and egg issue on releasing we'll have on API breaking 
change. People always building from source (like Debian) will have the issue 
also.

For demos, which are not really published during the release (just as 
documentation), disabling the module in the build when necessary is sufficient, 
won't change many things. For ant tasks, disabling the module will not publish 
the artifact: this will have a visible impact.

Regards,

Hervé

Le mercredi 15 novembre 2017, 23:05:14 CET Hervé BOUTEMY a écrit :
> 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
> 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 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
> maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider
> 4.0.0-SNAPSHOT that uses maven-resolver 2.0.0-SNAPSHOT with this new java
> package. Then try 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
> issue, but that is more subtle, then I chose to describe the most visible
> issue, with API breaking change)
> 
> IMHO, another consequence could be: maven-resolver-ant-tasks would perhaps
> better be versionned like maven-resolver-provider
> 
> 
> Merging resolver-demos is really the great big idea: with that merge,
> modifying maven-rresolver can immediately be tested with demos: that'll be
> so much easier to make changes to maven-resolver code!
> 
> Regards,
> 
> Hervé
> 
> Le mercredi 15 novembre 2017, 09:02:12 CET Michael Osipov a écrit :
> > Why -1 on the Ant tasks?
> > 
> > Am 2017-11-15 um 00:50 schrieb Hervé BOUTEMY:
> > > I answered on the mailing list and on the 2 Jira issues
> > > In summary, +1 to merge demos, -1 to merge ant-tasks
> > > 
> > > Regards,
> > > 
> > > Hervé
> > > 
> > > Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
> > >> Any feedback or should I just go ahead with the cleanup?
> > >> 
> > >> Manfred
> > >> 
> > >> Manfred Moser wrote on 2017-11-08 21:35:
> > >>> Hi all,
> > >>> 
> > >>> I have started and made good progress on getting Maven resolver all
> > >>> into
> > >>> the master branch instead of having master, demos and ant-tasks in
> > >>> separate branches.
> > >>> 
> > >>> Details are tracked in
> > >>> https://issues.apache.org/jira/browse/MRESOLVER-28
> > >>> 
> > >>> All of it is now in a new branch called master-all for you to see.
> > >>> 
> > >>> I am now wondering what the next steps are. I added what I think
> > >>> should
> > >>> happen next in the issue in a comment and would appreciate any input
> > >>> on
> > >>> the current setup and next steps.
> > >>> 
> > >>> Any help would be appreciated.
> > >>> 
> > >>> manfred
> > >> 
> > >> ---------------------------------------------------------------------
> > >> 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
> 
> ---------------------------------------------------------------------
> 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

Re: Maven resolver branch consolidation

Posted by Manfred Moser <ma...@simpligility.com>.

All done on the ant-tasks migration now as well. 

Next would be a release of the ant-tasks for which I filed https://issues.apache.org/jira/browse/MRESOLVER-37

Imho we should do that but I don't know what is involved and wont be able to work on it until some time in January. 

manfred

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

Re: Maven resolver branch consolidation

Posted by Manfred Moser <ma...@simpligility.com>.

All done on demos including cleanup and closing the issue.

For the ant tasks everything is ready in the new repo. If someone could set up the CI jenkins build that would be good.

Once we are happy I can delete the branch in the old repo.

And I think we also have to cut a release of the ant tasks. Not sure what it takes to do that.. the codebase seems ready from my point of view.. 

Manfred


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

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

please look at what I did in Doxia or skins: I chose to point to gitbox for 
connection and developerConnection and github for url
that's only a convention in our pom.xml: but gitbox and github work

Regards,

Hervé

Le samedi 25 novembre 2017, 23:08:27 CET Manfred Moser a écrit :
> Awesome ... setting up my github account and such now. In terms of pom.xml
> .. should the scm info just point to github then?
> 
> Manfred
> 
> Hervé BOUTEMY wrote on 2017-11-25 14:00:
> > ok, done: https://github.com/apache/maven-resolver-ant-tasks
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le samedi 25 novembre 2017, 22:07:12 CET Manfred Moser a écrit :
> >> So .. I tried this now. Seems like something on gitbox is not configured
> >> correctly for me because the Your PMCs drop down contains no entries
> >> apart
> >> from Your PMCs.
> >> 
> >> Can someone either fix this for me or create maven-resolver-ant-tasks
> >> repository? Then I can do the rest.
> >> 
> >> thx
> >> 
> >> manfred
> >> 
> >> Hervé BOUTEMY wrote on 2017-11-23 15:06:
> >> > yes, that's GitBox self service [1], easy to use, just:
> >> > 1. start by choosing your PMC before doing any other change (or you may
> >> > create a "maven-maven-something.git" like I did)
> >> > 2. change "GitHub notification list" to issues@maven.apache.org
> >> > 
> >> > the only issue I see is the mix of Artifact Resolver on git-wip and
> >> > Artifact Resolver Ant Tasks on gitbox: but one day, INFRA-15436 will
> >> > probably be done
> >> > 
> >> > Regards,
> >> > 
> >> > Hervé
> >> > 
> >> > [1] https://gitbox.apache.org/
> >> > 
> >> > Le jeudi 23 novembre 2017, 19:27:06 CET Stephen Connolly a écrit :
> >> >> Hervé might know... could be self-service on gitbox!
> >> >> 
> >> >> I have two repos to create after the Jenkins Server is upgraded on
> >> >> Sunday,
> >> >> so let me know the process
> >> >> 
> >> >> On Thu 23 Nov 2017 at 16:13, Manfred Moser <ma...@simpligility.com>
> > 
> > wrote:
> >> >> > So how do I make this repo copy happen? An infra ticket or something
> >> >> > like
> >> >> > that?
> >> >> > 
> >> >> > Stephen Connolly wrote on 2017-11-22 23:53:
> >> >> > > On Thu 23 Nov 2017 at 04:20, Manfred Moser
> >> >> > > <ma...@simpligility.com>
> >> >> > 
> >> >> > wrote:
> >> >> > >> Status update and questions:
> >> >> > >> 
> >> >> > >> - demos are all now in master and part of the multi module build
> >> >> > >> - no changes on the ant tasks for now
> >> >> > >> 
> >> >> > >> Questions:
> >> >> > >> 
> >> >> > >> 1. Can I delete the demos branch now or do we wait until next
> >> >> > >> release?
> >> >> > >> I
> >> >> > >> would prefer to delete the branch and close the ticket to be
> >> >> > >> honest.
> >> >> > >> 
> >> >> > >> 2. I like the idea of promoting the ant task from being hidden in
> >> >> > >> the
> >> >> > >> branch into their own repo. All we would have to do is to copy
> >> >> > >> the
> >> >> > 
> >> >> > existing
> >> >> > 
> >> >> > >> repo somehow into a new repo in apache git. Then we can dDelete
> >> >> > >> all
> >> >> > >> the
> >> >> > >> branches apart from the ant-task branch and make that the master.
> >> >> > >> Done.
> >> >> > 
> >> >> > I
> >> >> > 
> >> >> > >> am happy to do that in terms of the branches and so on but how do
> >> >> > >> I
> >> >> > >> go
> >> >> > >> about getting the repo copied into a new repo named
> >> >> > >> maven-resolver-ant-tasks?
> >> >> > > 
> >> >> > > I like that solution too
> >> >> > > 
> >> >> > >> Thanks
> >> >> > >> 
> >> >> > >> Manfred
> >> >> > >> 
> >> >> > >> -----------------------------------------------------------------
> >> >> > >> ---
> >> >> > >> -
> >> >> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> >> > >> For additional commands, e-mail: dev-help@maven.apache.org
> >> >> > >> 
> >> >> > >> --
> >> >> > > 
> >> >> > > Sent from my phone
> >> >> > 
> >> >> > --------------------------------------------------------------------
> >> >> > -
> >> >> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> >> > For additional commands, e-mail: dev-help@maven.apache.org
> >> >> > 
> >> >> > --
> >> >> 
> >> >> Sent from my phone
> >> > 
> >> > ---------------------------------------------------------------------
> >> > 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
> > 
> > ---------------------------------------------------------------------
> > 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



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

Re: Maven resolver branch consolidation

Posted by Manfred Moser <ma...@simpligility.com>.

Awesome ... setting up my github account and such now. In terms of pom.xml .. should the scm info just point to github then? 

Manfred

Hervé BOUTEMY wrote on 2017-11-25 14:00:

> ok, done: https://github.com/apache/maven-resolver-ant-tasks
> 
> Regards,
> 
> Hervé
> 
> Le samedi 25 novembre 2017, 22:07:12 CET Manfred Moser a écrit :
>> So .. I tried this now. Seems like something on gitbox is not configured
>> correctly for me because the Your PMCs drop down contains no entries apart
>> from Your PMCs.
>> 
>> Can someone either fix this for me or create maven-resolver-ant-tasks
>> repository? Then I can do the rest.
>> 
>> thx
>> 
>> manfred
>> 
>> Hervé BOUTEMY wrote on 2017-11-23 15:06:
>> > yes, that's GitBox self service [1], easy to use, just:
>> > 1. start by choosing your PMC before doing any other change (or you may
>> > create a "maven-maven-something.git" like I did)
>> > 2. change "GitHub notification list" to issues@maven.apache.org
>> > 
>> > the only issue I see is the mix of Artifact Resolver on git-wip and
>> > Artifact Resolver Ant Tasks on gitbox: but one day, INFRA-15436 will
>> > probably be done
>> > 
>> > Regards,
>> > 
>> > Hervé
>> > 
>> > [1] https://gitbox.apache.org/
>> > 
>> > Le jeudi 23 novembre 2017, 19:27:06 CET Stephen Connolly a écrit :
>> >> Hervé might know... could be self-service on gitbox!
>> >> 
>> >> I have two repos to create after the Jenkins Server is upgraded on
>> >> Sunday,
>> >> so let me know the process
>> >> 
>> >> On Thu 23 Nov 2017 at 16:13, Manfred Moser <ma...@simpligility.com> 
> wrote:
>> >> > So how do I make this repo copy happen? An infra ticket or something
>> >> > like
>> >> > that?
>> >> > 
>> >> > Stephen Connolly wrote on 2017-11-22 23:53:
>> >> > > On Thu 23 Nov 2017 at 04:20, Manfred Moser <ma...@simpligility.com>
>> >> > 
>> >> > wrote:
>> >> > >> Status update and questions:
>> >> > >> 
>> >> > >> - demos are all now in master and part of the multi module build
>> >> > >> - no changes on the ant tasks for now
>> >> > >> 
>> >> > >> Questions:
>> >> > >> 
>> >> > >> 1. Can I delete the demos branch now or do we wait until next
>> >> > >> release?
>> >> > >> I
>> >> > >> would prefer to delete the branch and close the ticket to be honest.
>> >> > >> 
>> >> > >> 2. I like the idea of promoting the ant task from being hidden in
>> >> > >> the
>> >> > >> branch into their own repo. All we would have to do is to copy the
>> >> > 
>> >> > existing
>> >> > 
>> >> > >> repo somehow into a new repo in apache git. Then we can dDelete all
>> >> > >> the
>> >> > >> branches apart from the ant-task branch and make that the master.
>> >> > >> Done.
>> >> > 
>> >> > I
>> >> > 
>> >> > >> am happy to do that in terms of the branches and so on but how do I
>> >> > >> go
>> >> > >> about getting the repo copied into a new repo named
>> >> > >> maven-resolver-ant-tasks?
>> >> > > 
>> >> > > I like that solution too
>> >> > > 
>> >> > >> Thanks
>> >> > >> 
>> >> > >> Manfred
>> >> > >> 
>> >> > >> --------------------------------------------------------------------
>> >> > >> -
>> >> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >> > >> For additional commands, e-mail: dev-help@maven.apache.org
>> >> > >> 
>> >> > >> --
>> >> > > 
>> >> > > Sent from my phone
>> >> > 
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >> > For additional commands, e-mail: dev-help@maven.apache.org
>> >> > 
>> >> > --
>> >> 
>> >> Sent from my phone
>> > 
>> > ---------------------------------------------------------------------
>> > 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
> 
> 
> 
> ---------------------------------------------------------------------
> 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

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

ok, done: https://github.com/apache/maven-resolver-ant-tasks

Regards,

Hervé

Le samedi 25 novembre 2017, 22:07:12 CET Manfred Moser a écrit :
> So .. I tried this now. Seems like something on gitbox is not configured
> correctly for me because the Your PMCs drop down contains no entries apart
> from Your PMCs.
> 
> Can someone either fix this for me or create maven-resolver-ant-tasks
> repository? Then I can do the rest.
> 
> thx
> 
> manfred
> 
> Hervé BOUTEMY wrote on 2017-11-23 15:06:
> > yes, that's GitBox self service [1], easy to use, just:
> > 1. start by choosing your PMC before doing any other change (or you may
> > create a "maven-maven-something.git" like I did)
> > 2. change "GitHub notification list" to issues@maven.apache.org
> > 
> > the only issue I see is the mix of Artifact Resolver on git-wip and
> > Artifact Resolver Ant Tasks on gitbox: but one day, INFRA-15436 will
> > probably be done
> > 
> > Regards,
> > 
> > Hervé
> > 
> > [1] https://gitbox.apache.org/
> > 
> > Le jeudi 23 novembre 2017, 19:27:06 CET Stephen Connolly a écrit :
> >> Hervé might know... could be self-service on gitbox!
> >> 
> >> I have two repos to create after the Jenkins Server is upgraded on
> >> Sunday,
> >> so let me know the process
> >> 
> >> On Thu 23 Nov 2017 at 16:13, Manfred Moser <ma...@simpligility.com> 
wrote:
> >> > So how do I make this repo copy happen? An infra ticket or something
> >> > like
> >> > that?
> >> > 
> >> > Stephen Connolly wrote on 2017-11-22 23:53:
> >> > > On Thu 23 Nov 2017 at 04:20, Manfred Moser <ma...@simpligility.com>
> >> > 
> >> > wrote:
> >> > >> Status update and questions:
> >> > >> 
> >> > >> - demos are all now in master and part of the multi module build
> >> > >> - no changes on the ant tasks for now
> >> > >> 
> >> > >> Questions:
> >> > >> 
> >> > >> 1. Can I delete the demos branch now or do we wait until next
> >> > >> release?
> >> > >> I
> >> > >> would prefer to delete the branch and close the ticket to be honest.
> >> > >> 
> >> > >> 2. I like the idea of promoting the ant task from being hidden in
> >> > >> the
> >> > >> branch into their own repo. All we would have to do is to copy the
> >> > 
> >> > existing
> >> > 
> >> > >> repo somehow into a new repo in apache git. Then we can dDelete all
> >> > >> the
> >> > >> branches apart from the ant-task branch and make that the master.
> >> > >> Done.
> >> > 
> >> > I
> >> > 
> >> > >> am happy to do that in terms of the branches and so on but how do I
> >> > >> go
> >> > >> about getting the repo copied into a new repo named
> >> > >> maven-resolver-ant-tasks?
> >> > > 
> >> > > I like that solution too
> >> > > 
> >> > >> Thanks
> >> > >> 
> >> > >> Manfred
> >> > >> 
> >> > >> --------------------------------------------------------------------
> >> > >> -
> >> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> > >> For additional commands, e-mail: dev-help@maven.apache.org
> >> > >> 
> >> > >> --
> >> > > 
> >> > > Sent from my phone
> >> > 
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: dev-help@maven.apache.org
> >> > 
> >> > --
> >> 
> >> Sent from my phone
> > 
> > ---------------------------------------------------------------------
> > 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



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

Re: Maven resolver branch consolidation

Posted by Manfred Moser <ma...@simpligility.com>.

So .. I tried this now. Seems like something on gitbox is not configured correctly for me because the Your PMCs drop down contains no entries apart from Your PMCs.

Can someone either fix this for me or create maven-resolver-ant-tasks repository? Then I can do the rest.

thx

manfred

Hervé BOUTEMY wrote on 2017-11-23 15:06:

> yes, that's GitBox self service [1], easy to use, just:
> 1. start by choosing your PMC before doing any other change (or you may create 
> a "maven-maven-something.git" like I did)
> 2. change "GitHub notification list" to issues@maven.apache.org
> 
> the only issue I see is the mix of Artifact Resolver on git-wip and Artifact 
> Resolver Ant Tasks on gitbox: but one day, INFRA-15436 will probably be done
> 
> Regards,
> 
> Hervé
> 
> [1] https://gitbox.apache.org/
> 
> Le jeudi 23 novembre 2017, 19:27:06 CET Stephen Connolly a écrit :
>> Hervé might know... could be self-service on gitbox!
>> 
>> I have two repos to create after the Jenkins Server is upgraded on Sunday,
>> so let me know the process
>> 
>> On Thu 23 Nov 2017 at 16:13, Manfred Moser <ma...@simpligility.com> wrote:
>> > So how do I make this repo copy happen? An infra ticket or something like
>> > that?
>> > 
>> > Stephen Connolly wrote on 2017-11-22 23:53:
>> > > On Thu 23 Nov 2017 at 04:20, Manfred Moser <ma...@simpligility.com>
>> > 
>> > wrote:
>> > >> Status update and questions:
>> > >> 
>> > >> - demos are all now in master and part of the multi module build
>> > >> - no changes on the ant tasks for now
>> > >> 
>> > >> Questions:
>> > >> 
>> > >> 1. Can I delete the demos branch now or do we wait until next release?
>> > >> I
>> > >> would prefer to delete the branch and close the ticket to be honest.
>> > >> 
>> > >> 2. I like the idea of promoting the ant task from being hidden in the
>> > >> branch into their own repo. All we would have to do is to copy the
>> > 
>> > existing
>> > 
>> > >> repo somehow into a new repo in apache git. Then we can dDelete all the
>> > >> branches apart from the ant-task branch and make that the master. Done.
>> > 
>> > I
>> > 
>> > >> am happy to do that in terms of the branches and so on but how do I go
>> > >> about getting the repo copied into a new repo named
>> > >> maven-resolver-ant-tasks?
>> > > 
>> > > I like that solution too
>> > > 
>> > >> Thanks
>> > >> 
>> > >> Manfred
>> > >> 
>> > >> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > >> For additional commands, e-mail: dev-help@maven.apache.org
>> > >> 
>> > >> --
>> > > 
>> > > Sent from my phone
>> > 
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: dev-help@maven.apache.org
>> > 
>> > --
>> 
>> Sent from my phone
> 
> 
> 
> ---------------------------------------------------------------------
> 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

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

yes, that's GitBox self service [1], easy to use, just:
1. start by choosing your PMC before doing any other change (or you may create 
a "maven-maven-something.git" like I did)
2. change "GitHub notification list" to issues@maven.apache.org

the only issue I see is the mix of Artifact Resolver on git-wip and Artifact 
Resolver Ant Tasks on gitbox: but one day, INFRA-15436 will probably be done

Regards,

Hervé

[1] https://gitbox.apache.org/

Le jeudi 23 novembre 2017, 19:27:06 CET Stephen Connolly a écrit :
> Hervé might know... could be self-service on gitbox!
> 
> I have two repos to create after the Jenkins Server is upgraded on Sunday,
> so let me know the process
> 
> On Thu 23 Nov 2017 at 16:13, Manfred Moser <ma...@simpligility.com> wrote:
> > So how do I make this repo copy happen? An infra ticket or something like
> > that?
> > 
> > Stephen Connolly wrote on 2017-11-22 23:53:
> > > On Thu 23 Nov 2017 at 04:20, Manfred Moser <ma...@simpligility.com>
> > 
> > wrote:
> > >> Status update and questions:
> > >> 
> > >> - demos are all now in master and part of the multi module build
> > >> - no changes on the ant tasks for now
> > >> 
> > >> Questions:
> > >> 
> > >> 1. Can I delete the demos branch now or do we wait until next release?
> > >> I
> > >> would prefer to delete the branch and close the ticket to be honest.
> > >> 
> > >> 2. I like the idea of promoting the ant task from being hidden in the
> > >> branch into their own repo. All we would have to do is to copy the
> > 
> > existing
> > 
> > >> repo somehow into a new repo in apache git. Then we can dDelete all the
> > >> branches apart from the ant-task branch and make that the master. Done.
> > 
> > I
> > 
> > >> am happy to do that in terms of the branches and so on but how do I go
> > >> about getting the repo copied into a new repo named
> > >> maven-resolver-ant-tasks?
> > > 
> > > I like that solution too
> > > 
> > >> Thanks
> > >> 
> > >> Manfred
> > >> 
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: dev-help@maven.apache.org
> > >> 
> > >> --
> > > 
> > > Sent from my phone
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> > 
> > --
> 
> Sent from my phone



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

Re: Maven resolver branch consolidation

Posted by Stephen Connolly <st...@gmail.com>.

Hervé might know... could be self-service on gitbox!

I have two repos to create after the Jenkins Server is upgraded on Sunday,
so let me know the process

On Thu 23 Nov 2017 at 16:13, Manfred Moser <ma...@simpligility.com> wrote:

> So how do I make this repo copy happen? An infra ticket or something like
> that?
>
> Stephen Connolly wrote on 2017-11-22 23:53:
>
> > On Thu 23 Nov 2017 at 04:20, Manfred Moser <ma...@simpligility.com>
> wrote:
> >
> >> Status update and questions:
> >>
> >> - demos are all now in master and part of the multi module build
> >> - no changes on the ant tasks for now
> >>
> >> Questions:
> >>
> >> 1. Can I delete the demos branch now or do we wait until next release? I
> >> would prefer to delete the branch and close the ticket to be honest.
> >>
> >> 2. I like the idea of promoting the ant task from being hidden in the
> >> branch into their own repo. All we would have to do is to copy the
> existing
> >> repo somehow into a new repo in apache git. Then we can dDelete all the
> >> branches apart from the ant-task branch and make that the master. Done.
> I
> >> am happy to do that in terms of the branches and so on but how do I go
> >> about getting the repo copied into a new repo named
> >> maven-resolver-ant-tasks?
> >
> >
> > I like that solution too
> >
> >>
> >>
> >> Thanks
> >>
> >> Manfred
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >> --
> > Sent from my phone
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
> --
Sent from my phone

Re: Maven resolver branch consolidation

Posted by Manfred Moser <ma...@simpligility.com>.

So how do I make this repo copy happen? An infra ticket or something like that? 

Stephen Connolly wrote on 2017-11-22 23:53:

> On Thu 23 Nov 2017 at 04:20, Manfred Moser <ma...@simpligility.com> wrote:
> 
>> Status update and questions:
>>
>> - demos are all now in master and part of the multi module build
>> - no changes on the ant tasks for now
>>
>> Questions:
>>
>> 1. Can I delete the demos branch now or do we wait until next release? I
>> would prefer to delete the branch and close the ticket to be honest.
>>
>> 2. I like the idea of promoting the ant task from being hidden in the
>> branch into their own repo. All we would have to do is to copy the existing
>> repo somehow into a new repo in apache git. Then we can dDelete all the
>> branches apart from the ant-task branch and make that the master. Done. I
>> am happy to do that in terms of the branches and so on but how do I go
>> about getting the repo copied into a new repo named
>> maven-resolver-ant-tasks?
> 
> 
> I like that solution too
> 
>>
>>
>> Thanks
>>
>> Manfred
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> --
> Sent from my phone
> 


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

Re: Maven resolver branch consolidation

Posted by Stephen Connolly <st...@gmail.com>.

On Thu 23 Nov 2017 at 04:20, Manfred Moser <ma...@simpligility.com> wrote:

> Status update and questions:
>
> - demos are all now in master and part of the multi module build
> - no changes on the ant tasks for now
>
> Questions:
>
> 1. Can I delete the demos branch now or do we wait until next release? I
> would prefer to delete the branch and close the ticket to be honest.
>
> 2. I like the idea of promoting the ant task from being hidden in the
> branch into their own repo. All we would have to do is to copy the existing
> repo somehow into a new repo in apache git. Then we can dDelete all the
> branches apart from the ant-task branch and make that the master. Done. I
> am happy to do that in terms of the branches and so on but how do I go
> about getting the repo copied into a new repo named
> maven-resolver-ant-tasks?


I like that solution too

>
>
> Thanks
>
> Manfred
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
> --
Sent from my phone

Re: Maven resolver branch consolidation

Posted by Manfred Moser <ma...@simpligility.com>.

Status update and questions:

- demos are all now in master and part of the multi module build
- no changes on the ant tasks for now

Questions:

1. Can I delete the demos branch now or do we wait until next release? I would prefer to delete the branch and close the ticket to be honest. 

2. I like the idea of promoting the ant task from being hidden in the branch into their own repo. All we would have to do is to copy the existing repo somehow into a new repo in apache git. Then we can dDelete all the branches apart from the ant-task branch and make that the master. Done. I am happy to do that in terms of the branches and so on but how do I go about getting the repo copied into a new repo named maven-resolver-ant-tasks? 

Thanks

Manfred

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

Re: Maven resolver branch consolidation

Posted by Michael Osipov <mi...@apache.org>.

Am 2017-11-15 um 23:05 schrieb Hervé BOUTEMY:
> 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
> 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
> can't release any maven-resolver API change that breaks maven-resolver-
>

Very good, leave it out. Move it to a separate repo.


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

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

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 
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 
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 
maven-resolver 2.0.0-SNAPSHOT, we need maven-resolver-provider 4.0.0-SNAPSHOT 
that uses maven-resolver 2.0.0-SNAPSHOT with this new java package. Then try 
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 issue, 
but that is more subtle, then I chose to describe the most visible issue, with 
API breaking change)

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


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

Regards,

Hervé

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



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

Re: Maven resolver branch consolidation

Posted by Michael Osipov <mi...@apache.org>.

Why -1 on the Ant tasks?

Am 2017-11-15 um 00:50 schrieb Hervé BOUTEMY:
> I answered on the mailing list and on the 2 Jira issues
> In summary, +1 to merge demos, -1 to merge ant-tasks
> 
> Regards,
> 
> Hervé
> 
> Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
>> Any feedback or should I just go ahead with the cleanup?
>>
>> Manfred
>>
>> Manfred Moser wrote on 2017-11-08 21:35:
>>> Hi all,
>>>
>>> I have started and made good progress on getting Maven resolver all into
>>> the master branch instead of having master, demos and ant-tasks in
>>> separate branches.
>>>
>>> Details are tracked in https://issues.apache.org/jira/browse/MRESOLVER-28
>>>
>>> All of it is now in a new branch called master-all for you to see.
>>>
>>> I am now wondering what the next steps are. I added what I think should
>>> happen next in the issue in a comment and would appreciate any input on
>>> the current setup and next steps.
>>>
>>> Any help would be appreciated.
>>>
>>> manfred
>>
>> ---------------------------------------------------------------------
>> 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
> 
> 



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

Re: Maven resolver branch consolidation

Posted by Hervé BOUTEMY <he...@free.fr>.

I answered on the mailing list and on the 2 Jira issues
In summary, +1 to merge demos, -1 to merge ant-tasks

Regards,

Hervé

Le mardi 14 novembre 2017, 18:19:40 CET Manfred Moser a écrit :
> Any feedback or should I just go ahead with the cleanup?
> 
> Manfred
> 
> Manfred Moser wrote on 2017-11-08 21:35:
> > Hi all,
> > 
> > I have started and made good progress on getting Maven resolver all into
> > the master branch instead of having master, demos and ant-tasks in
> > separate branches.
> > 
> > Details are tracked in https://issues.apache.org/jira/browse/MRESOLVER-28
> > 
> > All of it is now in a new branch called master-all for you to see.
> > 
> > I am now wondering what the next steps are. I added what I think should
> > happen next in the issue in a comment and would appreciate any input on
> > the current setup and next steps.
> > 
> > Any help would be appreciated.
> > 
> > manfred
> 
> ---------------------------------------------------------------------
> 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

Re: Maven resolver branch consolidation

Posted by Manfred Moser <ma...@simpligility.com>.

Any feedback or should I just go ahead with the cleanup?

Manfred

Manfred Moser wrote on 2017-11-08 21:35:

> Hi all,
> 
> I have started and made good progress on getting Maven resolver all into the
> master branch instead of having master, demos and ant-tasks in separate
> branches.
> 
> Details are tracked in https://issues.apache.org/jira/browse/MRESOLVER-28
> 
> All of it is now in a new branch called master-all for you to see.
> 
> I am now wondering what the next steps are. I added what I think should happen
> next in the issue in a comment and would appreciate any input on the current
> setup and next steps. 
> 
> Any help would be appreciated.
> 
> manfred


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