You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@maven.org> on 2007/11/06 12:19:44 UTC
Using a graph to resolve dependencies
Mark, Ralph,
You'll probably be interested in the artifact graph code that went in
as the conflict resolution and dependency management are natural fall
outs of the work. The old code works perfectly fine and I just have to
obfuscate a couple JARs and I can publish a little dependency viewer
that Oleg whipped off with a donated version of yFiles. Once we put
that up then I think we can visually see the behavior of the mechanism
and work through the flaws by seeing them. We can make some pictures
and then throw out the scenarios for discussion. After the tree is
produced, creating a graph with conflict resolution techniques is
pretty straight forward but deciding how the POM should change to have
the various conflict resolvers activated will require a bit of dialog
I imagine.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Using a graph to resolve dependencies
Posted by Jason van Zyl <ja...@maven.org>.
On 6 Nov 07, at 6:30 AM 6 Nov 07, Ralph Goers wrote:
> Are there specific examples to illustrate how this works? i.e. are
> there unit tests for it? Obviously I'm definitely interested in this.
>
There be a full example of use in the tool I'm going to package up. It
will be a code example and a visual way for us to decide what's best
in terms of strategy.
> Ralph
>
> Jason van Zyl wrote:
>> Mark, Ralph,
>>
>> You'll probably be interested in the artifact graph code that went
>> in as the conflict resolution and dependency management are natural
>> fall outs of the work. The old code works perfectly fine and I just
>> have to obfuscate a couple JARs and I can publish a little
>> dependency viewer that Oleg whipped off with a donated version of
>> yFiles. Once we put that up then I think we can visually see the
>> behavior of the mechanism and work through the flaws by seeing
>> them. We can make some pictures and then throw out the scenarios
>> for discussion. After the tree is produced, creating a graph with
>> conflict resolution techniques is pretty straight forward but
>> deciding how the POM should change to have the various conflict
>> resolvers activated will require a bit of dialog I imagine.
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Using a graph to resolve dependencies
Posted by Ralph Goers <Ra...@dslextreme.com>.
Are there specific examples to illustrate how this works? i.e. are there
unit tests for it? Obviously I'm definitely interested in this.
Ralph
Jason van Zyl wrote:
> Mark, Ralph,
>
> You'll probably be interested in the artifact graph code that went in
> as the conflict resolution and dependency management are natural fall
> outs of the work. The old code works perfectly fine and I just have to
> obfuscate a couple JARs and I can publish a little dependency viewer
> that Oleg whipped off with a donated version of yFiles. Once we put
> that up then I think we can visually see the behavior of the mechanism
> and work through the flaws by seeing them. We can make some pictures
> and then throw out the scenarios for discussion. After the tree is
> produced, creating a graph with conflict resolution techniques is
> pretty straight forward but deciding how the POM should change to have
> the various conflict resolvers activated will require a bit of dialog
> I imagine.
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> 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