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

["SCHNEKENBURGER Remi 211865" <Remi.SCHNEKENBURGER@xxxxxx>]

Hi folks, 

I was also interested in that mail exchange, but was unfortunately disconnected from the net this weekend.
I had the same problem for Orbit, giving the repo address during buckminster build that was not the "latest" official one. I don't expect to change the build map just 5 minutes before official release, this can introduce lots of mistakes. 

For the repo dependency, this would be effectively nice to have +0, +1, ... repo during milestones build. Unfortunately, I depend on +3 projects. So I do not know how it could happen if the repositories were build on a one-shot process, with the problem of depending on one exact feature number.

Topic separation in Thomas's mail sounds good to me.

Cheers,
Rémi



-----Message d'origine-----
De : cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] De la part de Eike Stepper
Envoyé : lundi 20 décembre 2010 09:55
À : Cross project issues
Objet : Re: [cross-project-issues-dev] dependencies, build and P2

Am 20.12.2010 09:50, schrieb Thomas Hallgren:
> 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. 
Apologies, these releng things are not my main task.

> "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.
Seems so.

>
> Perhaps we should split the discussion into several threads, and if possible move those threads to a smaller forum?
We can. Suggestions?

But I'm a bit worried that no more than four persons have participated so far. Would that mean others don't have these problems or they just don't care? :P

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev