|Re: [cross-project-issues-dev] dependencies, build and P2|
Am 19.12.2010 11:44, schrieb Thomas Hallgren:
On 2010-12-19 11:14, Eike Stepper wrote: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?In my proposed scenario, the orbit repository (and thus "all Orbit stuff") is available as input to all builds. The final step is still the b3 aggregation. It uses the p2 planner to create a transitive scope extending from all included features and strip of all excess bundles from the final Indigo repository.
That's what I understood.
No references to Orbit will be necessary anywhere.
But I have a lot of stuff that can't be in Indigo. For these things I have our own public repo (the same one that we contribute to Indigo from). Wouldn't I need to reference Orbit somehow from there? Cheers /Eike ---- http://www.esc-net.de http://thegordian.blogspot.com http://twitter.com/eikestepper
Back to the top