[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] dependencies, build and P2
|
On 2010-12-20 09:08, Eike Stepper wrote:
Am 20.12.2010 09:05, schrieb Thomas Hallgren:
On 2010-12-20 08:25, Eike Stepper wrote:
... just causes a failure if the required components are not already there. Seems I was wrong?
Yes, that's wrong. You use the old (before p2) non-greedy interpretation of a requirement. Today, p2 will always
install what's missing since it treats requirements as greedy.
Oh! So, why don't we all just convert "include derby 10.5.1.v2010nnnnn" to "require derby [10.0.0,11.0.0)" then?
Why don't you remove that requirement altogether and rely on what's expressed in your bundle requirements?
- thomas
- References:
- [cross-project-issues-dev] conflicting dependencies to Orbit
- Re: [cross-project-issues-dev] conflicting dependencies to Orbit
- Re: [cross-project-issues-dev] conflicting dependencies to Orbit
- [cross-project-issues-dev] dependencies, build and P2
- Re: [cross-project-issues-dev] dependencies, build and P2
- Re: [cross-project-issues-dev] dependencies, build and P2
- Re: [cross-project-issues-dev] dependencies, build and P2
- Re: [cross-project-issues-dev] dependencies, build and P2
- Re: [cross-project-issues-dev] dependencies, build and P2
- Re: [cross-project-issues-dev] dependencies, build and P2
- Re: [cross-project-issues-dev] dependencies, build and P2
- Re: [cross-project-issues-dev] dependencies, build and P2
- Re: [cross-project-issues-dev] dependencies, build and P2
- Re: [cross-project-issues-dev] dependencies, build and P2
- Re: [cross-project-issues-dev] dependencies, build and P2