[
https://issues.apache.org/jira/browse/FOR-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565281#action_12565281
]
David Crossley commented on FOR-1068:
-------------------------------------
One solution might be to use Apache Ant and Apache Ivy, coupled with the ASF
mirror system. See http://www.apache.org/dev/mirrors.html
To start a demo, i followed the above doc to create a script which determines
(using GeoIP) the nearest available mirrors for a particular client.
http://people.apache.org/~crossley/ivy-forrest-plugin/mirrors--xml.cgi
which generates an xml file. The first listed is the preferred mirror, then
other available mirrors, then the two default mirrors.
Our Ant build could transform this to generate an Ivy "resolvers" file to list
each mirrored artefact using a "url resolver". Ivy would then manage the plugin
download and do the md5 checksum.
> plugins need to be managed via the ASF mirror system
> ----------------------------------------------------
>
> Key: FOR-1068
> URL: https://issues.apache.org/jira/browse/FOR-1068
> Project: Forrest
> Issue Type: Bug
> Components: Plugins (general issues), Project administration
> Reporter: David Crossley
>
> Forrest Plugins need to be deployed and downloaded via the ASF mirror system.
> See http://www.apache.org/dev/mirrors.html
> There are a number of reasons for this, e.g. being kind to the
> infrastructure; faster local access. However, the main reason is that this is
> where official PMC releases are required to be.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
