[
https://issues.apache.org/jira/browse/UIMA-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867742#comment-13867742
]
Peter Klügl commented on UIMA-3534:
-----------------------------------
Sounds reasonable, but it would maybe be easier if the link is specified in the
composite repository.
I know that this solution is not preferred, but I wanted to mention it anyway.
If we have one update site for each release, then the composite repository can
simply point to the update sites on the archive site, I think. dist.apache.org
would then only contain the latest update site.
> better Eclipse plugin version management
> ----------------------------------------
>
> Key: UIMA-3534
> URL: https://issues.apache.org/jira/browse/UIMA-3534
> Project: UIMA
> Issue Type: Brainstorming
> Components: Eclipse plugins
> Reporter: Marshall Schor
> Priority: Minor
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
