Sorry,

 

the Ivy build was fixed in  <https://issues.apache.org/jira/browse/LUCENE-8807> 
https://issues.apache.org/jira/browse/LUCENE-8807 (Lucene/Solr 8.2), the Maven 
POMs were fixed:  <https://issues.apache.org/jira/browse/LUCENE-8993> 
https://issues.apache.org/jira/browse/LUCENE-8993 (Lucene/Solr 8.3)

 

Sorry both links pointed to same diff. The history is above.

 

So in short: to build Solr from source you need 8.2, otherwise Ivy won’t find 
any Restlet artifacts. To use the Maven POMs in 3rd party projects, you need 
8.3.

 

Uwe

 

-----

Uwe Schindler

Achterdiek 19, D-28357 Bremen

https://www.thetaphi.de

eMail: [email protected]

 

From: Uwe Schindler <[email protected]> 
Sent: Saturday, December 28, 2019 12:07 AM
To: 'Joel Bernstein' <[email protected]>; 'lucene dev' <[email protected]>
Subject: RE: maven issues with org.restlet.jee:org.restlet

 

Hi,

 

there are few issues:

*       Java does not support redirects from HTTP -> HTTPS. It simply won’t 
follow those. This is a known issue and well-known. This was the reason why I 
changed all URLs to HTTPS in recently, as any redirect won’t work.  We can’t 
change that for old Solr releases, they keep broken. I changed this here 
(possible since 8.3.0):  
<https://github.com/apache/lucene-solr/commit/4a015e224dcd4b1c5f3db92c01d8bf80be3c244a>
 
https://github.com/apache/lucene-solr/commit/4a015e224dcd4b1c5f3db92c01d8bf80be3c244a.
 The Maven POMs were changed a bit later:  
<https://github.com/apache/lucene-solr/commit/4a015e224dcd4b1c5f3db92c01d8bf80be3c244a>
 
https://github.com/apache/lucene-solr/commit/4a015e224dcd4b1c5f3db92c01d8bf80be3c244a.
 So basically everything after 8.3.0 should work correct, older versions cannot 
be fixed anymore. The change to talend is not the issue, it’s the HTTP->HTTPS 
one which breaks Ivy.
*       This is no longer an issue with pure Maven (as they have a workaround), 
but Ivy can’t handle that (as it relies on Java’s own URL handling). Newer 
Maven has its own one.
*       The HTTPS stuff redirects to the talend URL and finally it’s internally 
handled by Cloudfront. And it looks like it breaks there. With Lucene/Solr 
Master on Java 11 I get no error. I think Java 8 does not support TLS 1.3 and 
cloudfront wants this. No idea at all. But it works here.

 

Uwe

 

-----

Uwe Schindler

Achterdiek 19, D-28357 Bremen

https://www.thetaphi.de

eMail: [email protected] <mailto:[email protected]> 

 

From: Joel Bernstein <[email protected] <mailto:[email protected]> > 
Sent: Friday, December 27, 2019 9:17 PM
To: lucene dev <[email protected] <mailto:[email protected]> >
Cc: Uwe Schindler <[email protected] <mailto:[email protected]> >
Subject: Re: maven issues with org.restlet.jee:org.restlet

 

Agreed, if they don't fix this it needs to be removed, this is a mess.

 

I did some more digging and the files are present when you point a browser at:

 

https://maven.restlet.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar

https://maven.restlet.org/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar
 
<https://maven.restlet.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar>
 

http://maven.restlet.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar
 
<https://maven.restlet.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar>
 

http://maven.restlet.org/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar
 
<https://maven.restlet.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar>
 

 

The error I get is a handshake failure which is a failure to connect through 
the Maven java libraries. So, something about how they're hosting these files 
seems to be problematic.

 

Joel Bernstein

http://joelsolr.blogspot.com/

 

 

On Fri, Dec 27, 2019 at 2:10 PM Ishan Chattopadhyaya <[email protected] 
<mailto:[email protected]> > wrote:

Let us find out and eliminate all uses of restlet from Solr. I don't think we 
should be relying on any dependency that is not published to Maven Central.

 

On Sat, 28 Dec, 2019, 12:32 AM Joel Bernstein, <[email protected] 
<mailto:[email protected]> > wrote:

Ok, thanks.

 

I'll dig around some more and see if I find a solution. And I'll complain to 
them for sure. 

 




Joel Bernstein

http://joelsolr.blogspot.com/

 

 

On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[email protected] 
<mailto:[email protected]> > wrote:

No idea. Complaint at them for breaking millions of builds.

They should really post their stuff to Maven Central. No idea why they don't do 
this.

Uwe

Am December 27, 2019 6:54:04 PM UTC schrieb Joel Bernstein <[email protected] 
<mailto:[email protected]> >:

Yeah this a crazy way for them to manage dependencies.

 

I see the old URL now redirects to https://maven.restlet.talend.com/.

 

I tried adding the repo to my POM as follows:

 

<repositories>
        <repository>
          <id>maven-restlet</id>
          <name>Restlet repository</name>
          <url>https://maven.restlet.talend.com</url>
</repository>

 

And still get the handshake error. I tried http and still get the same 
handshake error.

 

Any thoughts on what to try next?

 

 

 

 




Joel Bernstein

http://joelsolr.blogspot.com/

 

 

 

 

 

On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[email protected] 
<mailto:[email protected]> > wrote:

I figured out they again changed urls. No to talend.

This is a big issue and should reported that this horrible company, sorry! This 
is a no go for maven dependencies. The reason is that Java handles redirection 
in a bad way. So never ever change urls for branding purposes! Sorry Talked: 
bad idea, revert this…!

Uwe

Uwe

Am December 27, 2019 6:42:49 PM UTC schrieb Uwe Schindler <[email protected] 
<mailto:[email protected]> >:

This should be fixed with newer versions of Solr. The reason is missing https 
and this causes some redirection problems.

Maybe you are using a Solr version with a POM that still refers to non 
encrypted artifact repos.

This was driving me crazy when I changed the remote repositories a whole ago, 
too.

Uwe

Am December 27, 2019 6:33:32 PM UTC schrieb Joel Bernstein <[email protected] 
<mailto:[email protected]> >:

I'm currently building an outside project that uses the solrj and solr-core 
dependencies. I'm getting the following errors when attempting build the 
project on a jenkins server:

 

Failed to read artifact descriptor for org.restlet.jee:org.restlet:jar:2.3.0: 
Could not transfer artifact org.restlet.jee:org.restlet:pom:2.3.0 from/to 
maven-restlet ( <http://maven.restlet.org/> http://maven.restlet.org): Received 
fatal alert: handshake_failure

 

Has anyone ran into the restlet resolution issues when resolving Solr 
dependencies before and found the fix?

 




Joel Bernstein

http://joelsolr.blogspot.com/


--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de


--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de


--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de

Reply via email to