[jira] [Resolved] (DIRSTUDIO-1055) Investigate usage of mirrors for update site

["Stefan Seelmann (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRSTUDIO-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seelmann resolved DIRSTUDIO-1055.
----------------------------------------
       Resolution: Not A Problem
    Fix Version/s:     (was: 2.0.0-M10)
         Assignee: Stefan Seelmann

The problem with invalid mirror is none. I tested on staging, and there the mirror list seems to be outdated. On production website everything works fine.

I'll create another issue regarding the https problem. 

> Investigate usage of mirrors for update site
> --------------------------------------------
>
>                 Key: DIRSTUDIO-1055
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1055
>             Project: Directory Studio
>          Issue Type: Task
>          Components: studio-updatesite
>    Affects Versions: 2.0.0-M9 (2.0.0.v20150606-M9)
>            Reporter: Stefan Seelmann
>            Assignee: Stefan Seelmann
>
> Apache projects should use mirrors for downloads. We use them for normal download pages, and also for Eclipse update site.
> A mirror can be down. On the normal download page that is no big problem, a reload of the page chooses another mirror.
> But with Eclipse update site it is different: If the mirror is not available it just shows "No content", only the log shows an error. Even worse is that Eclipse remembers the URL and reuses it. I had bad luck to get apache.myamplifiers.com (INFRA-9804) which isn't working, and also after Eclipse restart it continued to contact that site.
> We have to investigate a better way how to use mirros for the update site. Maybe it can be configured that it isn't retried.
> In the meantime I'll configure the update site to use "www.apache.org/dist", this will at least distribute downloads to two servers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)