Community
Participate
Working Groups
I'm opening this request as a consequence of issues discussed in bug 330288. Seems to me it'd be better overall if EPP Packaging used /releases/staging repo solely as the source of its builds. Granted, it is partially selfish, so that EPP packaging provides an "early test" of the repo. But, also ... how else can we know the packages accurately contain what others would end up with, if they installed things "manually". Obviously, we could write tests to test the repo, and we could write tests to ensure the contents were the same ... but, seems easier just to make it part of the process instead of testing after the fact.
I partially fixed this on Sunday and hit the first problem, see bug 347311. 'Partially': The p2 director call that assembles the packages has a reduced set of p2 repository, one is /releases/staging, the other one is the (at this time not yet released, temporary) EPP p2 repository. Not yet fixed is the first part of the EPP build, it uses /releases/staging *and* a deep link to a Eclipse Platform p2 repository (ie. download.eclipse.org/eclipse/update/3.7milestones/foo.bar/...). I'd like to remove this next, but that needs additional testing which is not possible on the day before RC2. Moving to RC3.
This had been fixed in the Indigo EPP package builds, whereas I didn't change anything in the EPP repository build at that point. The Juno EPP repository build *and* the Juno EPP package build have no references to any other p2 repositories other than /releases/staging (and EPP itself). Closing as FIXED. (Remark... in *milestone* builds I am sometimes adding an additional project specific repository to help projects getting out their package build. But this is done in milestone builds only!)
