[
https://issues.apache.org/jira/browse/UIMA-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871302#comment-13871302
]
Marshall Schor commented on UIMA-3534:
--------------------------------------
I think this (one update site per release, per component) is how the IvyDE
project does it. See, for instance, their composite repository file:
http://www.apache.org/dist/ant/ivyde/updatesite/.
Adopting this approach would require updating the composite site every release,
to have it point to the child versions in the archive (except for the current
release).
The downside of this is that the number of subsites would be larger - and all
of them would need to be accessed when the composite site was referenced, to
read their content / artifact files. When installing, the installer would need
to read
- old way: 1 composite site * 2 files (content & artifacts) + 2 * number of
subsites
- ivy way: 1 composite site * 2 files (content & artifacts) + 2 * number of
subsites * the number of releases in each subsite
I suppose we could limit this by having a limited number of older releases
included in the composite list. The older ones would still be there, if needed.
> 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)
