Re: [cross-project-issues-dev] dependencies, build and P2

[Miles Parker <milesparker@xxxxxxxxx>]

Yes, that all makes a lot of sense. What you're saying is that the very first thing that happens is that a P2 repos is made available that contains all of the Orbit bundles, and perhaps even some other core stuff. Everyone points to that, and maybe we even share a common rmap which includes very well constrained paths to what is in there. In a way that's kind of a -1 build, as we expect Orbit to be quite stable, given that it automatically has to go through IP process, etc.. 

On Dec 19, 2010, at 2:44 AM, Thomas Hallgren wrote:

> 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. No references to Orbit will be necessary anywhere.
> 
> - thomas
> 
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev