Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Suggestion: Consider providing "latest" p2 repositories


> Not only would this make builds and target platforms resolution faster

I generally dig into the individual composite files and use the latest
manually to speed up builds and target resolution.

I would also go further than Ed's proposal. In addition to
download.e.o having "latest" directories, that we use the "latests" in
the shipped products. So instead of being used as the URL in
the packages, that
is used.

IIRC for people looking to adopt this within their own project, you
can't have links in because they don't mirror
properly, so you need composite xmls/jars in the latest directory (as
Ed's EMF example does).

Jonah Graham
Kichwa Coders Ltd.

On 14 March 2018 at 14:14, Ed Merks <ed.merks@xxxxxxxxx> wrote:
> Hi,
> I wanted to make a suggestion to the folks maintaining update sites on
>   Of course almost all projects provide various
> composite p2 repositories for different "build qualities" such as releases,
> milestones, integration, stable, and nightly builds.  Even when well managed
> though, these repositories can grow to include a significantly large number
> of child repositories.  We often use such composite repository URLs in our
> builds, target platforms, and Oomph's targlets, but in most cases, we're
> really only interested in the latest version of each installable unit for
> some specific build quality.  I.e., in most cases we'd be better off if each
> of such composite had a corresponding "latest" composite that pointed to a
> single simple repository containing the latest release, milestone,
> integration, stable, or nightly build.  Not only would this make builds and
> target platforms resolution faster, would be better
> utilized by serving only content and artifact metadata for the composite and
> for the single simple repo, rather serving n + 1 of these where n can tend
> toward umpteen, e.g., as in
> where the composite
> contains 211 repos.   As an existing example,
> points to the latest release,
> although it currently points to a composite that in turn contain 3 releases
> (which is kind of fishy because there are more releases of Oxygen than are
> included in the composite).
> Please consider providing such a convenience to your consumers and please
> consider using them if/when available;  the server will
> thank you by providing better performance.   If you're depending on EMF, EMF
> is already provides a "latest" for each of its composites:
> Regards,
> Ed
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit

Back to the top