As Mark further explained, I think his proposal is entirely different
and could be adapted to whatever strategy you apply in general here.
However, I wanted to pick up on this:
On 25/04/2007, at 2:36 PM, Jason van Zyl wrote:
But ultimately what is currently there must be replaced by a system
that does not alter the graph while the graph is forming. By this I
mean the entire graph must be resolved first and any subsequent
transformation whether that be scope state changes, version
alignment, and repository ordering must be done using standard
graph transformation.
Agreed. The case today is probably more a problem of premature
optimisation (reading the whole graph when you are going to throw
things away is time consuming when you need to download all the
associated poms). So reading the whole graph then applying conflict
resolvers, etc. is a better strategy - though it may require we work
more on the metadata to make it less messy.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
