[
https://issues.apache.org/jira/browse/UIMA-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871313#comment-13871313
]
Marshall Schor commented on UIMA-3534:
--------------------------------------
One more thought: if a composite site could reference a child composite site,
then we could have a more-or-less stable top-level composite site which is like
it is now, pointing to multi-module child projects; those, in turn would have a
composite site which designated children by version, and was updated to keep
just the current release version on the mirror system, and the older ones in
the archive.
This would require some testing - to see if it worked (e.g., having a composite
site's child be, in turn, another composite 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)
