For the meta-data, order doesn't matter since that would break the
whole idea of using a SAT algorithm to come up with a resolution. p2
will build a set of all UI's in the repository (composite or not),
and then feed that to the SAT solver. The solver then comes up with
a plan. The order of children doesn't affect the content of the set.
For the artifacts, I know that url's with 'file:' are consulted
first so that unnecessary download traffic is avoided. I'm almost
certain that with the 'file' priority out of the way, the artifact
repositories are consulted in the order they are listed.
On 2011-02-19 08:01, David M Williams wrote:
In particular, is it
part of the "spec"
or API? (That is, I'm not just asking about current
I think this issue will become
relevant, especially for eclipse.org, now that p2 is getting
:) because some repos that were on 'downloads' should at some
move to 'archives'.
Let me elaborate. In a composite
many of us might have child repos that might be similar to the
fictional URLs ...
Is that order, above, treated differently
order, below? Which repo is searched (or matched) first for
This can become important, for
if some artifact is the same in all three repositories ....
that is, the
version/qualifier is unchanged. If the "archive" repos are
first, then the result would not be mirrored, and always come
directly, it seems. The opposite would be desired, that
would be "searched/matched" first, and if found there, then,
via the magic of the mirrors URL, would have a chance of
coming from a
mirror, thus being faster for many users (and off-loading some
So, is there a way to make sure
URLs are matched first? Should they come first in list, or
last ... or
is the outcome indeterminable?
Feel free to comment in bug
which was opened some time ago to "investigate" this issue ...
but, I'm hoping some p2 expert knows the answer, and I won't
have to investigate
p2-dev mailing list