Details
-
Brainstorming
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Our current Eclipse update site design has one file tree -and under that, several individual big-project (e.g. uimaj, ruta, etc) subsites, each having an independent update site just for that project.
The subsites have (today) all the versions of the plugins/features. As time marches on, the subsites can grow large due to older versions. I think we need a way to follow the spirit of Apache mirroring, and keep just the current or active releases on the mirrors, and have a seamless way to access the older things on the apache archive.
There may be a fairly painless way to do this if we can have each subsite "link" to the archive site, and let Eclipse do the merging. It would be good if we could set this up so the normal way of managing this (i.e., you delete the older releases from the dist.apache.org/ svn, and the disappear from the mirrors, but are still on the archive site.