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

Junhong Xu updated HBASE-22069:
-------------------------------
    Description: 
Just as [~elserj] said in HBASE-22038 ,
{quote}archive.a.o should not be used by build processes. www-us.apache.org is 
a load-balanced endpoint, whereas archive.a.o is a single service.We should 
just switch to newer versions of these libraries that still exist on 
www-us.apache.org. Would you be able to try that change out in a follow-on?
{quote}
 

And as the comment from [~busbey] there has been a script fix the problem as  
the title.

  was:
Just as [~elserj] said in HBASE-22038 ,
{quote}archive.a.o should not be used by build processes. www-us.apache.org is 
a load-balanced endpoint, whereas archive.a.o is a single service.We should 
just switch to newer versions of these libraries that still exist on 
www-us.apache.org. Would you be able to try that change out in a follow-on?
{quote}
 

update resource versions that downloading from [http://www-us.apache.org/] 
which are absent instead of Downloading them from archive.apache.org.


> fix the download resource absences from Apache urls by scripts automatically
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-22069
>                 URL: https://issues.apache.org/jira/browse/HBASE-22069
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Junhong Xu
>            Assignee: Junhong Xu
>            Priority: Major
>
> Just as [~elserj] said in HBASE-22038 ,
> {quote}archive.a.o should not be used by build processes. www-us.apache.org 
> is a load-balanced endpoint, whereas archive.a.o is a single service.We 
> should just switch to newer versions of these libraries that still exist on 
> www-us.apache.org. Would you be able to try that change out in a follow-on?
> {quote}
>  
> And as the comment from [~busbey] there has been a script fix the problem as  
> the title.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to