+1
On Thu, Nov 16, 2017 at 11:48 AM, Robert Scholte
wrote:
> +1
>
>
>
> On Thu, 16 Nov 2017 18:24:09 +0100, Hervé BOUTEMY
> wrote:
>
> I updated MNG-6302 implementation:
>> see https://issues.apache.org/jira/browse/MNG-6302
>>
>> are there seconders for this implementation?
>> or ideas on bette
+1
On Thu, 16 Nov 2017 18:24:09 +0100, Hervé BOUTEMY
wrote:
I updated MNG-6302 implementation:
see https://issues.apache.org/jira/browse/MNG-6302
are there seconders for this implementation?
or ideas on better displays?
Regards,
Hervé
---
I updated MNG-6302 implementation:
see https://issues.apache.org/jira/browse/MNG-6302
are there seconders for this implementation?
or ideas on better displays?
Regards,
Hervé
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apac
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 on
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 C
On Thu 16 Nov 2017 at 07:51, Hervé BOUTEMY 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
> cha
