Community
Participate
Working Groups
It will have to happen eventually ... with "real" repositories, ... so maybe we should investigate and "experiment" with Indigo milestone builds. The idea is that we want things retrievable from some p2 URL, such as /releases/helios to always be retrievable from that URL ... but, that does not mean the artifacts themselves have to reside on the prime real estate of the download server (where they are mirrored to about 100 different places). While we want the "old" releases available, we would not expect them to be requested very often, so they could move to the archives server. All it takes is a little programming :) to come up with a script "move" the artifacts to archives, and then update the metadata (which would remain on download server, so there is a constant URL) so p2 knows where to fetch the actual artifact from. There would be no "mirrorsURL" attribute in the artifact repositories on archives. Any volunteers?
As I think about, it, this would be (almost) insanely easy. Since our "public" repository is a composite repo that "points to" subdirectories, all we need to do is copy that subdirectory to "archives" and then change the URL to be a full URL, instead of a relative url to a subdirectory. For example, <children size='3'> <child location='201011120900'/> <child location='201010010900'/> <child location='201008200901'/> </children> could become <children size='3'> <child location='201011120900'/> <child location='201010010900'/> <child location='http://archive.eclipse.org/releases/indigo/201008200901'/> </children> One complication to think though ... we do refer to some other's repos (EPP and Platform's) ... but I think there would be no hard need to change our "internal" URLs, as long as those projects follow the same process of making sure their external facing repo URL stays true ... even once they to move their artifacts to archives. (In fact, now that I think about it, these was one of the reasons we wanted to have each release in a subdirectory ... so it would be easy to move to archives location).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
I do still want to do this, and document the process in case others want to do similar. (I know some that have, already, such as Orbit, and EGit).
This is still work that needs to be done, by someone, so removed "stalebug" from whiteboard.
This should be doable if needed, but will assign to 'nobody' since I do not plan to do it (at least, any time soon).
Repositories can move to archive.e.o and retain download.e.o links, as we have transparent redirects.
