Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] dependencies, build and P2

So, that brings us back to the former statement that we would like to:

a) Only inlucde our own features/bundles into our feature.xmls
b) Not use any feature dependencies

And to be able to do that we need either all Orbit stuff in the release train repo (through a mechanism outside of our builds) or be allowed to refer to the Oribt repo directly from our feature.xmls (updateURL?, discoveryURL?, ...?)

Does that make sense?



Am 19.12.2010 10:40, schrieb Thomas Hallgren:
I'm also questioning the use of feature requirements. I can see one (somewhat far fetched) use of it and that is when all bundle inter-dependencies are expressed as packages rather than bundles. By adding feature requirements, one can encourage that those packages are provided by certain bundles. I say encourage because there's no way to guarantee that this actually happens when other bundles also provide the same packages.

In the old days, a feature requirement was interpreted as 'non-greedy', i.e. the thing had to be present in the install in order to install your feature but there would be no attempt to install it. Unless they were met, the installation would fail immediately. For some reason that interpretation is no longer valid. The feature requirements are greedy so their role is IMO very questionable.

- thomas

On 2010-12-19 10:29, Gunnar Wagenknecht wrote:
Am 19.12.2010 09:19, schrieb Eike Stepper:
I see that there are plugin and feature dependencies possible. Would
you say that the plugin dependcies are a relict from times before p2?
Frankly, I'm constantly asking myself the same question. They definitely
existed before p2. As far as I remember the old update manager used
those dependencies. p2 should't need them as it is capable of collecting
all the dependencies by using the meta-data produced from the bundle


cross-project-issues-dev mailing list

Back to the top