maven issues with org.restlet.jee:org.restlet

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

maven issues with org.restlet.jee:org.restlet

Joel Bernstein
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): Received fatal alert: handshake_failure

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


Reply | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Uwe Schindler
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 <[hidden email]>:
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): Received fatal alert: handshake_failure

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



--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de
Reply | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Uwe Schindler
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 <[hidden email]>:
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 <[hidden email]>:
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): Received fatal alert: handshake_failure

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



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

--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de
Reply | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Joel Bernstein
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?










On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]>:
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): Received fatal alert: handshake_failure

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



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

--
Uwe Schindler
Achterdiek 19, 28357 Bremen
https://www.thetaphi.de
Reply | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Uwe Schindler
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 <[hidden email]>:
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?










On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]>:
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): Received fatal alert: handshake_failure

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



--
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 | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Joel Bernstein
Ok, thanks.

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




On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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?










On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]>:
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): Received fatal alert: handshake_failure

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



--
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 | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Ishan Chattopadhyaya
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, <[hidden email]> wrote:
Ok, thanks.

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




On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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?










On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]>:
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): Received fatal alert: handshake_failure

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



--
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 | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Joel Bernstein
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:


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.


On Fri, Dec 27, 2019 at 2:10 PM Ishan Chattopadhyaya <[hidden email]> 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, <[hidden email]> wrote:
Ok, thanks.

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




On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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?










On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]>:
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): Received fatal alert: handshake_failure

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



--
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 | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Joel Bernstein
But if you go to the directory rather then file you see the redirection to:


This redirection is likely the problem, as Uwe mentioned.





On Fri, Dec 27, 2019 at 3:16 PM Joel Bernstein <[hidden email]> wrote:
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:


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.


On Fri, Dec 27, 2019 at 2:10 PM Ishan Chattopadhyaya <[hidden email]> 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, <[hidden email]> wrote:
Ok, thanks.

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




On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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?










On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]>:
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): Received fatal alert: handshake_failure

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



--
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 | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Joel Bernstein
Older versions of Solr can also not be built from from ivy. This is from a 7.1 build:

[ivy:retrieve] ==== maven.restlet.org: tried

[ivy:retrieve]   http://maven.restlet.org/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.pom

[ivy:retrieve]   -- artifact org.restlet.jee#org.restlet.ext.servlet;2.3.0!org.restlet.ext.servlet.jar:

[ivy:retrieve]   http://maven.restlet.org/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.jar

[ivy:retrieve] ==== sonatype-releases: tried

[ivy:retrieve]   https://oss.sonatype.org/content/repositories/releases/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.pom

[ivy:retrieve]   -- artifact org.restlet.jee#org.restlet.ext.servlet;2.3.0!org.restlet.ext.servlet.jar:

[ivy:retrieve]   https://oss.sonatype.org/content/repositories/releases/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.jar

[ivy:retrieve] ==== releases.cloudera.com: tried

[ivy:retrieve]   http://repository.cloudera.com/content/repositories/releases/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.pom

[ivy:retrieve]   -- artifact org.restlet.jee#org.restlet.ext.servlet;2.3.0!org.restlet.ext.servlet.jar:

[ivy:retrieve]   http://repository.cloudera.com/content/repositories/releases/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.jar

[ivy:retrieve] ==== working-chinese-mirror: tried

[ivy:retrieve]   http://uk.maven.org/maven2/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.pom

[ivy:retrieve]   -- artifact org.restlet.jee#org.restlet.ext.servlet;2.3.0!org.restlet.ext.servlet.jar:

[ivy:retrieve]   http://uk.maven.org/maven2/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.jar

[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::

[ivy:retrieve] ::          UNRESOLVED DEPENDENCIES         ::

[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::

[ivy:retrieve] :: org.restlet.jee#org.restlet;2.3.0: not found

[ivy:retrieve] :: org.restlet.jee#org.restlet.ext.servlet;2.3.0: not found

[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::

[ivy:retrieve] 

[ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS





On Fri, Dec 27, 2019 at 3:18 PM Joel Bernstein <[hidden email]> wrote:
But if you go to the directory rather then file you see the redirection to:


This redirection is likely the problem, as Uwe mentioned.





On Fri, Dec 27, 2019 at 3:16 PM Joel Bernstein <[hidden email]> wrote:
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:


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.


On Fri, Dec 27, 2019 at 2:10 PM Ishan Chattopadhyaya <[hidden email]> 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, <[hidden email]> wrote:
Ok, thanks.

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




On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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?










On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]>:
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): Received fatal alert: handshake_failure

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



--
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 | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Joel Bernstein
I updated this ticket:


If I don't hear back soon, I'll create a new ticket specific to the Solr issues.


On Fri, Dec 27, 2019 at 4:07 PM Joel Bernstein <[hidden email]> wrote:
Older versions of Solr can also not be built from from ivy. This is from a 7.1 build:

[ivy:retrieve] ==== maven.restlet.org: tried

[ivy:retrieve]   http://maven.restlet.org/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.pom

[ivy:retrieve]   -- artifact org.restlet.jee#org.restlet.ext.servlet;2.3.0!org.restlet.ext.servlet.jar:

[ivy:retrieve]   http://maven.restlet.org/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.jar

[ivy:retrieve] ==== sonatype-releases: tried

[ivy:retrieve]   https://oss.sonatype.org/content/repositories/releases/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.pom

[ivy:retrieve]   -- artifact org.restlet.jee#org.restlet.ext.servlet;2.3.0!org.restlet.ext.servlet.jar:

[ivy:retrieve]   https://oss.sonatype.org/content/repositories/releases/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.jar

[ivy:retrieve] ==== releases.cloudera.com: tried

[ivy:retrieve]   http://repository.cloudera.com/content/repositories/releases/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.pom

[ivy:retrieve]   -- artifact org.restlet.jee#org.restlet.ext.servlet;2.3.0!org.restlet.ext.servlet.jar:

[ivy:retrieve]   http://repository.cloudera.com/content/repositories/releases/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.jar

[ivy:retrieve] ==== working-chinese-mirror: tried

[ivy:retrieve]   http://uk.maven.org/maven2/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.pom

[ivy:retrieve]   -- artifact org.restlet.jee#org.restlet.ext.servlet;2.3.0!org.restlet.ext.servlet.jar:

[ivy:retrieve]   http://uk.maven.org/maven2/org/restlet/jee/org.restlet.ext.servlet/2.3.0/org.restlet.ext.servlet-2.3.0.jar

[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::

[ivy:retrieve] ::          UNRESOLVED DEPENDENCIES         ::

[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::

[ivy:retrieve] :: org.restlet.jee#org.restlet;2.3.0: not found

[ivy:retrieve] :: org.restlet.jee#org.restlet.ext.servlet;2.3.0: not found

[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::

[ivy:retrieve] 

[ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS





On Fri, Dec 27, 2019 at 3:18 PM Joel Bernstein <[hidden email]> wrote:
But if you go to the directory rather then file you see the redirection to:


This redirection is likely the problem, as Uwe mentioned.





On Fri, Dec 27, 2019 at 3:16 PM Joel Bernstein <[hidden email]> wrote:
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:


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.


On Fri, Dec 27, 2019 at 2:10 PM Ishan Chattopadhyaya <[hidden email]> 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, <[hidden email]> wrote:
Ok, thanks.

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




On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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?










On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]>:
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): Received fatal alert: handshake_failure

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



--
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 | Threaded
Open this post in threaded view
|

RE: maven issues with org.restlet.jee:org.restlet

Uwe Schindler
In reply to this post by Joel Bernstein

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. The Maven POMs were changed a bit later: 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: [hidden email]

 

From: Joel Bernstein <[hidden email]>
Sent: Friday, December 27, 2019 9:17 PM
To: lucene dev <[hidden email]>
Cc: Uwe Schindler <[hidden email]>
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:

 

 

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.

 

 

On Fri, Dec 27, 2019 at 2:10 PM Ishan Chattopadhyaya <[hidden email]> 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, <[hidden email]> wrote:

Ok, thanks.

 

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

 


 

 

On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:

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?

 

 

 

 


 

 

 

 

 

On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:

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 <[hidden email]>:

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): Received fatal alert: handshake_failure

 

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

 



--
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 | Threaded
Open this post in threaded view
|

RE: maven issues with org.restlet.jee:org.restlet

Uwe Schindler

Sorry,

 

the Ivy build was fixed in 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 (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: [hidden email]

 

From: Uwe Schindler <[hidden email]>
Sent: Saturday, December 28, 2019 12:07 AM
To: 'Joel Bernstein' <[hidden email]>; 'lucene dev' <[hidden email]>
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. The Maven POMs were changed a bit later: 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: [hidden email]

 

From: Joel Bernstein <[hidden email]>
Sent: Friday, December 27, 2019 9:17 PM
To: lucene dev <[hidden email]>
Cc: Uwe Schindler <[hidden email]>
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:

 

 

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.

 

 

On Fri, Dec 27, 2019 at 2:10 PM Ishan Chattopadhyaya <[hidden email]> 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, <[hidden email]> wrote:

Ok, thanks.

 

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

 


 

 

On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:

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?

 

 

 

 


 

 

 

 

 

On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:

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 <[hidden email]>:

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): Received fatal alert: handshake_failure

 

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

 



--
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 | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Joel Bernstein
Ok Uwe, 

I think I've got all the details. I'll open a ticket with the restlet project explaining the http->https redirect problem. Hopefully they will fix this and put this problem to rest (pun intended).

I'll also open a Solr ticket so we can discuss what can be done to possibly mitigate this issue without the help of the restlet project and to discuss the removal of this dependency.

Thanks!


 




On Fri, Dec 27, 2019 at 6:11 PM Uwe Schindler <[hidden email]> wrote:

Sorry,

 

the Ivy build was fixed in 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 (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: [hidden email]

 

From: Uwe Schindler <[hidden email]>
Sent: Saturday, December 28, 2019 12:07 AM
To: 'Joel Bernstein' <[hidden email]>; 'lucene dev' <[hidden email]>
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. The Maven POMs were changed a bit later: 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: [hidden email]

 

From: Joel Bernstein <[hidden email]>
Sent: Friday, December 27, 2019 9:17 PM
To: lucene dev <[hidden email]>
Cc: Uwe Schindler <[hidden email]>
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:

 

 

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.

 

 

On Fri, Dec 27, 2019 at 2:10 PM Ishan Chattopadhyaya <[hidden email]> 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, <[hidden email]> wrote:

Ok, thanks.

 

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

 


 

 

On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:

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?

 

 

 

 


 

 

 

 

 

On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:

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 <[hidden email]>:

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): Received fatal alert: handshake_failure

 

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

 



--
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 | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Joel Bernstein

On Sat, Dec 28, 2019 at 1:17 PM Joel Bernstein <[hidden email]> wrote:
Ok Uwe, 

I think I've got all the details. I'll open a ticket with the restlet project explaining the http->https redirect problem. Hopefully they will fix this and put this problem to rest (pun intended).

I'll also open a Solr ticket so we can discuss what can be done to possibly mitigate this issue without the help of the restlet project and to discuss the removal of this dependency.

Thanks!


 




On Fri, Dec 27, 2019 at 6:11 PM Uwe Schindler <[hidden email]> wrote:

Sorry,

 

the Ivy build was fixed in 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 (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: [hidden email]

 

From: Uwe Schindler <[hidden email]>
Sent: Saturday, December 28, 2019 12:07 AM
To: 'Joel Bernstein' <[hidden email]>; 'lucene dev' <[hidden email]>
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. The Maven POMs were changed a bit later: 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: [hidden email]

 

From: Joel Bernstein <[hidden email]>
Sent: Friday, December 27, 2019 9:17 PM
To: lucene dev <[hidden email]>
Cc: Uwe Schindler <[hidden email]>
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:

 

 

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.

 

 

On Fri, Dec 27, 2019 at 2:10 PM Ishan Chattopadhyaya <[hidden email]> 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, <[hidden email]> wrote:

Ok, thanks.

 

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

 


 

 

On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:

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?

 

 

 

 


 

 

 

 

 

On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:

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 <[hidden email]>:

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): Received fatal alert: handshake_failure

 

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

 



--
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 | Threaded
Open this post in threaded view
|

Re: maven issues with org.restlet.jee:org.restlet

Joel Bernstein
Let's move the discussion to this ticket:


On Sat, Dec 28, 2019 at 1:31 PM Joel Bernstein <[hidden email]> wrote:

On Sat, Dec 28, 2019 at 1:17 PM Joel Bernstein <[hidden email]> wrote:
Ok Uwe, 

I think I've got all the details. I'll open a ticket with the restlet project explaining the http->https redirect problem. Hopefully they will fix this and put this problem to rest (pun intended).

I'll also open a Solr ticket so we can discuss what can be done to possibly mitigate this issue without the help of the restlet project and to discuss the removal of this dependency.

Thanks!


 




On Fri, Dec 27, 2019 at 6:11 PM Uwe Schindler <[hidden email]> wrote:

Sorry,

 

the Ivy build was fixed in 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 (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: [hidden email]

 

From: Uwe Schindler <[hidden email]>
Sent: Saturday, December 28, 2019 12:07 AM
To: 'Joel Bernstein' <[hidden email]>; 'lucene dev' <[hidden email]>
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. The Maven POMs were changed a bit later: 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: [hidden email]

 

From: Joel Bernstein <[hidden email]>
Sent: Friday, December 27, 2019 9:17 PM
To: lucene dev <[hidden email]>
Cc: Uwe Schindler <[hidden email]>
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:

 

 

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.

 

 

On Fri, Dec 27, 2019 at 2:10 PM Ishan Chattopadhyaya <[hidden email]> 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, <[hidden email]> wrote:

Ok, thanks.

 

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

 


 

 

On Fri, Dec 27, 2019 at 1:57 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:

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?

 

 

 

 


 

 

 

 

 

On Fri, Dec 27, 2019 at 1:46 PM Uwe Schindler <[hidden email]> 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 <[hidden email]>:

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 <[hidden email]>:

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): Received fatal alert: handshake_failure

 

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

 



--
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