Re: [cross-project-issues-dev] Suggestion: Consider providing "latest" p

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

+1

> 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
http://download.eclipse.org/releases/oxygen/ being used as the URL in
the packages, that http://download.eclipse.org/releases/oxygen/latest
is used.

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


Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com


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
> download.eclipse.org.   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, download.eclipse.org 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
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=532213 where the composite
> contains 211 repos.   As an existing example,
> http://download.eclipse.org/releases/latest 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 download.eclipse.org 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:
> http://download.eclipse.org/modeling/emf/emf/builds/index.html
>
> 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
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev