The latest trunk seems to work after blowing away the ivy cache
folders. So, must have been a metadata poisoning.

Thank you for the suggestions, I did not think of anything outside of
the actual subversion folder as being the contributing factor.

Regards,
   Alex.
----
Sign up for my Solr resources newsletter at http://www.solr-start.com/


On 8 January 2015 at 04:52, Vanlerberghe, Luc
<[email protected]> wrote:
> I had exactly the same issue building Solr, but using the tips here I managed 
> to get everything working again:
>
> I deleted the .ant and .ivy2 folders in my user directory, edited 
> lucene\ivy-settings.xml to comment out the <ibiblio name"cloudera" ... /> and 
> <resolver ref="cloudera"/> elements (leave the elements for 
> "releases.cloudera.com" !)
>
> After that "ant ivy-bootstrap" and "ant resolve" ran successfully (taking 
> about 5 minutes to download all dependencies)
>
> I guess that one of the artifacts loaded from "cloudera" conflicts with one 
> of the official ones from "releases.cloudera.com" (perhaps the order in the 
> resolver chain should be reversed?)
>
> Side note: For "releases.cloudera.com", Mark Miller changed https to http on 
> 14/3/2014 to work around an expired SSL certificate.
> I checked the certificate on the site and switched back to using https and it 
> seems to be fine now...
>
> Regards,
>
> Luc
>
> -----Original Message-----
> From: Alexandre Rafalovitch [mailto:[email protected]]
> Sent: donderdag 8 januari 2015 6:32
> To: [email protected]
> Subject: [Possibly spoofed] Re: Anybody having troubles building trunk?
>
> Similar but different? I got rid of cloudera references all together,
> did "ant clean" and it is still the same error.
>
> The build line that failed is:
>
> <ivy:retrieve conf="compile,compile.hadoop" type="jar,bundle"
> sync="${ivy.sync}" log="download-only" symlink="${ivy.symlink}"/>
>
> in trunk/solr/core/build.xml:65
>
> Regards,
>    Alex.
> ----
> Sign up for my Solr resources newsletter at http://www.solr-start.com/
>
>
> On 8 January 2015 at 00:12, Steve Rowe <[email protected]> wrote:
>> I had the same issue earlier today, and identified the problem here, along
>> with a workaround:
>> <https://issues.apache.org/jira/browse/SOLR-4839?focusedCommentId=14268311&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14268311>
>>
>> On Wed, Jan 7, 2015 at 10:36 PM, Alexandre Rafalovitch <[email protected]>
>> wrote:
>>>
>>> I am having dependencies issues even if I blow away everything, check
>>> it out again and do 'ant resolve':
>>> resolve:
>>> [ivy:retrieve]
>>> [ivy:retrieve] :: problems summary ::
>>> [ivy:retrieve] :::: WARNINGS
>>> [ivy:retrieve]         ::::::::::::::::::::::::::::::::::::::::::::::
>>> [ivy:retrieve]         ::          UNRESOLVED DEPENDENCIES         ::
>>> [ivy:retrieve]         ::::::::::::::::::::::::::::::::::::::::::::::
>>> [ivy:retrieve]         ::
>>> org.restlet.jee#org.restlet.ext.servlet;2.3.0: configuration not found
>>> in org.restlet.jee#org.restlet.ext.servlet;2.3.0: 'master'. It was
>>> required from org.apache.solr#core;[email protected]
>>> compile
>>> [ivy:retrieve]         ::::::::::::::::::::::::::::::::::::::::::::::
>>> [ivy:retrieve]
>>> [ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
>>>
>>> BUILD FAILED
>>>
>>> Regards,
>>>    Alex.
>>>
>>> ----
>>> Sign up for my Solr resources newsletter at http://www.solr-start.com/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to