[
https://issues.apache.org/jira/browse/SOLR-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270058#comment-14270058
]
Mark Miller commented on SOLR-4839:
-----------------------------------
bq. Order Cloudera resolver after Sonatype and Restlet.
It's funny - this is one of the first things I tried yesterday and it did not
seem to help. Perhaps some initial user error somehow. Today it seems to change
things for me. It also worked to add a force=true to the restlet repo, but that
is also super slow and silly.
bq. should we also remove the cloudera resolver and only keep the
releases.cloudera.com one?
If we only need one, let's only have one. I'm not sure the genesis of both,
other than that is what was in our initial downstream Cloudera Search repo.
Would be great to remove one if it has popular 3rd party libs in it and we
don't need it. Certainly helped confuse debugging this issue.
> Jetty 9
> -------
>
> Key: SOLR-4839
> URL: https://issues.apache.org/jira/browse/SOLR-4839
> Project: Solr
> Issue Type: Improvement
> Reporter: Bill Bell
> Assignee: Shalin Shekhar Mangar
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-4839-fix-eclipse.patch, SOLR-4839.patch,
> SOLR-4839.patch, SOLR-4839.patch, SOLR-4839.patch, SOLR-4839.patch,
> SOLR-4839.patch, SOLR-4839.patch, SOLR-4839.patch, SOLR-4839.patch
>
>
> Implement Jetty 9
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
