[
https://issues.apache.org/jira/browse/UIMA-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16175334#comment-16175334
]
Marshall Schor commented on UIMA-5550:
--------------------------------------
brainstorming a strategy to archive older eclipse releases. The apache main
way to do archiving is to a) require new things to have new names (version
suffixes, for example) and then delete the old ones (the delete goes to the
main Apache mirrored main distribution page, but the archive copy of that page
is not updated - so the older version remains there.
To use this approach for eclipse web sites, it would seem that each sub-site
would need to have a version number as part of its name. Then we could
occasionally advance the version number and start over with new releases.
Example:
Version 2 of uimaj plugins has (currently) plugins for 2.3.1, 2.4.0, 2.4.1,
2.4.2, 2.5.0, 2.6.0, 2.7.0, 2.8.0, 2.8.1, 2.9.0, 2.10.0, and 2.10.1. version
3 of uimaj plugins has currently just 3.0.0-alpha02.
Some of these for v2 should be removed - they had bugs and were quickly
replaced (e.g. 2.8.0, 2.4.1).
A possible "process" might be to take a large subsite that needs pruning, and
use it to create a new subsite, named
subsite-name-xxx-yyy where xxx and yyy might give hints on the range of
versions included. So for instance, we might create uimaj-archive-2.3.1-2.9.0
as a new subsite, and populate it with those versions, and delete those from
the uimaj subsite. Once the Apache archive system has copied the changes to
the archive, then uimaj-archive-2.3.1-2.9.0 could be deleted (from the mirror
master, but it would remain in the archive).
This site
https://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_repositorytasks.htm
shows some eclipse ant tasks (need to be run with the eclipse ant runner app)
that can selectively "mirror" (or copy) installable units (which can be
specified using version), and another ant task that can delete installalble
units.
So with some work, this should be doable I think.
People needing to install archived versions would need to navigate to the
proper archive subsite, and use that as the eclipse install target.
Does this seem like a reasonable approach? Better approaches welcome :-)
> Eclipse Update Site improvement for 3.0.0SDK
> --------------------------------------------
>
> Key: UIMA-5550
> URL: https://issues.apache.org/jira/browse/UIMA-5550
> Project: UIMA
> Issue Type: Task
> Components: Eclipse plugins
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 3.0.0SDK
>
>
> Figure out how to drop the older versions (alpha and beta) from the eclipse
> update site for 3.0.0.
> Decide on a naming convention for the 3.0.0 "branch" if keeping separate.
> Figure out how to move older versions for v2 Uima to "archive" spot, not in
> the Apache "mirrors".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
