[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Unexpected resolution failure
- From: "Oberlies, Tobias" <tobias.oberlies@xxxxxxx>
- Date: Thu, 13 Oct 2011 11:35:27 +0200
- Accept-language: en-US, de-DE
- Acceptlanguage: en-US, de-DE
- Delivered-to: firstname.lastname@example.org
- Thread-index: Acx59FfkAmqajJnlR5Owq0AB/IKB6QAAiZyAAJE3JaADU+tI4A==
- Thread-topic: Unexpected resolution failure
Katya Todorova wrote:
> It seems that 0.0.0 is interpreted as [184.108.40.206109261256,
> 220.127.116.11109261256] instead of [0.0.0, infinity) and p2 resolver doesn't
> make an attempt to find a solution containing lower version.
> Is that the expected behavior?
0.0.0 can be a version or a version range. 0.0.0 as version is a fixed version - the latest one available when querying a metadata repo, 0.0.0 as version range is an open version range.
You need to know what you are specifying (version vs. Version range) to know the semantics.