|Re: [cross-project-issues-dev] dependencies, build and P2|
On 2010-12-20 09:28, Eike Stepper wrote:
The p2 repo produced by my build currently *contains* copies of javax.servlet, derby, h2 and other third party stuff that is needed by my users. I'm really not happy about this duplication but in the end I have to ensure that my users can easily install my features/bundles. Note that only part of my features is contributed to Indigo. Often users want to newer integration builds directly from my own p2 repos or they want to use something that can not go to / be in Indigo. As of now Orbit itself is not in Indigo and I may not add discovery URLs to my features that point outside of Indigo. So, how can I prevent that a user who wants to install my project doesn't just see the p2 error "Can not install for unsatisfied requirements"?
I think I answered that before. "a composite that adds in the Orbit repo would of course be an option. Another is to use the b3 aggregator and create a self sufficient repository that contains only the things needed by your stuff."
I think the discussion is all spanning several topics now. Here's what I think we've been discussing so far: 1. A proposed infrastructure that would simplify Indigo builds. 2. Feature includes versus dependencies expressed as feature requirements or bundle requirements. 3. How to make Orbit bundles available to end users when Indigo isn't used. 4. How to populate a target platform for the build. Perhaps we should split the discussion into several threads, and if possible move those threads to a smaller forum? - thomas
Back to the top