Thanks for the summary mail, Mark. I agree that's the general plan. A
couple of comments...
On 20/06/2007, at 2:48 AM, Mark Hobson wrote:
other than that let's just choose one of the libraries and deprecate
the other one to avoid splitting the work
archiva-dependency-graph appears to be qu
Hi Joakim,
On 19/06/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
I want to see maven 2.1 fixed in regards to project model resolution.
The current mess in maven/components is completely unusable within
archiva. If that occurs, then the rest of the dependency graph
resolution bits will fall int
Mark Hobson wrote:
On 19/06/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
On 6/19/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
> Ah thanks, I wasn't aware of that - I had assumed archiva used
> dependency-tree, although I haven't got around to looking at archiva
> yet. That certainly looks like t
The list of resolved dependencies is equivalent to what maven has.
And speaking of different resolutions, even now, maven 2.0.5 and 2.0.6
resolve differently. In my tests 2.0.6 does a worse job choosing the
'latest' version of a dep when in conflict, maven 2.0.5 picks correctly.
When I say
On 19/06/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
On 6/19/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
> Ah thanks, I wasn't aware of that - I had assumed archiva used
> dependency-tree, although I haven't got around to looking at archiva
> yet. That certainly looks like the kind of code I wa
On 6/19/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
Hi Joakim,
On 19/06/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
> Note, Archiva couldn't use the DependencyTree component, as it made
> assumptions about repository access, availability, search order, and
> layout that simply were not true. (a
Hi Joakim,
On 19/06/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
Note, Archiva couldn't use the DependencyTree component, as it made
assumptions about repository access, availability, search order, and
layout that simply were not true. (actually, this is a problem mostly in
maven/components, bu
Note, Archiva couldn't use the DependencyTree component, as it made
assumptions about repository access, availability, search order, and
layout that simply were not true. (actually, this is a problem mostly in
maven/components, but it still affected Archiva).
So, we wrote our own dependency gr
Hi Kenney,
On 16/06/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Hi,
Just a quick question as to what this is for?
maven-dependency-tree is the shared component for computing dependency
trees from Maven's artifact resolution. The original code came from
project-info-reports:dependencies,
On 15/06/07, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
Go for it. If you change some public APIs, try if possible to deprecate them
(in the case of some users used them)
Sure, but there has been some major refactoring so it may not be possible.
Mark
--
Hi,
Just a quick question as to what this is for?
Is it used in 'help:dependencies'?
Is it/will it be used in maven-core?
I see the dependency plugin uses both dependency-tree and dependency-analyzer,
what's the relation?
If maven core eventually uses this, shouldn't it be moved into maven-co
, 2007 10:42 AM
To: Maven Developers List
Subject: Re: maven-dependency-tree changes for 1.1
On 13/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I've been working on dependency tree diagnostic tools and as a
> consequence have made substantial changes to maven
No problems here.
-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Friday, June 15, 2007 10:42 AM
To: Maven Developers List
Subject: Re: maven-dependency-tree changes for 1.1
On 13/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I
On 13/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
Hi there,
I've been working on dependency tree diagnostic tools and as a
consequence have made substantial changes to maven-dependency-tree. A
brief synopsis of changes are:
- support for node states: included, omitted for conflict, etc.
- no
14 matches
Mail list logo
