Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of arafalov@gmail.com designates
 209.85.220.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAAD-Smwf3sS=uLrwcwFLa69eoeXh4EsbqRvhY4GbYYrTUJab8A@mail.gmail.com>
References: 
 <CAAD-Smwf3sS=uLrwcwFLa69eoeXh4EsbqRvhY4GbYYrTUJab8A@mail.gmail.com>
From: Alexandre Rafalovitch <arafalov@gmail.com>
Date: Sun, 30 Nov 2014 00:47:45 -0500
Message-ID: 
 <CAEFAe-G5rWL=9coHHQJPo7_++axnvvGOg0xeQGH7g90MxoaU8A@mail.gmail.com>
Subject: Re: Solr Compile error
To: solr-user <solr-user@lucene.apache.org>
Content-Type: text/plain; charset=UTF-8

Is it possible you have a corporate firewall? And Java is not picking
up automatic proxy?

Regards,
   Alex.
P.s. The repo error I think is normal. Some weird Maven thing in general.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources and newsletter: http://www.solr-start.com/ and @solrstart
Solr popularizers community: https://www.linkedin.com/groups?gid=6713853


On 30 November 2014 at 00:41, Darx Oman <darxoman@gmail.com> wrote:
> Hi there
> when I "ant compile" solr 4.10.x, I got the following error:
>
> ------------------------------------------------------------------------------------------------------------------------------------------
> ivy-availability-check:
>      [echo] Building solr-core...
>
> ivy-fail:
>
> ivy-fail:
>
> ivy-configure:
> [ivy:configure] :: loading settings :: file =
> E:\Solr\Solr_4_10_Source\lucene\ivy-settings.xml
>
> resolve:
> [ivy:retrieve]
> [ivy:retrieve] :: problems summary ::
> [ivy:retrieve] :::: WARNINGS
> [ivy:retrieve]          [FAILED     ]
> org.restlet.jee#org.restlet;2.1.1!org.restlet.jar:  (0ms)
> [ivy:retrieve]  ==== shared: tried
> [ivy:retrieve]
> C:\Users\Me.MyPC\.ivy2\shared\org.restlet.jee\org.restlet\2.1.1\jars\org.restlet.jar
> [ivy:retrieve]  ==== public: tried
> [ivy:retrieve]
> http://repo1.maven.org/maven2/org/restlet/jee/org.restlet/2.1.1/org.restlet-2.1.1.jar
> [ivy:retrieve]          [FAILED     ]
> org.restlet.jee#org.restlet.ext.servlet;2.1.1!org.restlet.ext.servlet.jar:
> (0ms)
> [ivy:retrieve]  ==== shared: tried
> [ivy:retrieve]
> C:\Users\Me.MyPC\.ivy2\shared\org.restlet.jee\org.restlet.ext.servlet\2.1.1\jars\org.restlet.ext.servlet.jar
> [ivy:retrieve]  ==== public: tried
> [ivy:retrieve]
> http://repo1.maven.org/maven2/org/restlet/jee/org.restlet.ext.servlet/2.1.1/org.restlet.ext.servlet-2.1.1.jar
> [ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve]          ::              FAILED DOWNLOADS            ::
> [ivy:retrieve]          :: ^ see resolution messages for details  ^ ::
> [ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve]          :: org.restlet.jee#org.restlet;2.1.1!org.restlet.jar
> [ivy:retrieve]          ::
> org.restlet.jee#org.restlet.ext.servlet;2.1.1!org.restlet.ext.servlet.jar
> [ivy:retrieve]          ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:retrieve]
> [ivy:retrieve]
> [ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
>
> BUILD FAILED
> E:\Solr\Solr_4_10_Source\build.xml:119: The following error occurred while
> executing this line:
> E:\Solr\Solr_4_10_Source\solr\common-build.xml:365: The following error
> occurred while executing this line:
> E:\Solr\Solr_4_10_Source\solr\core\build.xml:65: impossible to resolve
> dependencies:
>         resolve failed - see output for details
>
> Total time: 10 seconds
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> what I noticed is that this link does not exist.
> "
> http://repo1.maven.org/maven2/org/restlet/jee/org.restlet.ext.servlet/2.1.1/org.restlet.ext.servlet-2.1.1.jar
> "
>
> even when browsing "http://repo1.maven.org/", I got a page that says:
>
> Browsing for this directory has been disabled.
> View this directory's contents on http://search.maven.org instead.
>
> any ideas how to overcome this error?