[
https://issues.apache.org/jira/browse/JCR-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911009#comment-17911009
]
Julian Reschke commented on JCR-5122:
-------------------------------------
We did a similar change for the transition from 3.x to 4.x. Note that this
required deprecation first (and a rather long wait period).
I agree though that this needs to be done eventually.
Maybe break it down into smaller tasks like:
- use new Apache Http components server-side
- create a new client library (new package) based on JDK client, deprecate old
- finally, and much later, remove use of old client (note that this will be a
breaking change)
> Get rid of Apache HTTP Client dependency
> ----------------------------------------
>
> Key: JCR-5122
> URL: https://issues.apache.org/jira/browse/JCR-5122
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-spi2dav, jackrabbit-webdav
> Reporter: Konrad Windszus
> Priority: Major
>
> Instead of Apache HTTP Client (in the outdated 4.5.x version) we should
> leverage the Java-built-in HTTP Client:
> https://docs.oracle.com/en/java/javase/11/docs/api/java.net.http/java/net/http/HttpClient.html
> See also https://hc.apache.org/status.html
> bq. Users of HttpClient 4.x are strongly encouraged to migrate to HttpClient
> 5.x
> Such a change cannot be backwards-compatible as the exposed API (e.g.
> https://github.com/apache/jackrabbit/blob/trunk/jackrabbit-webdav/src/main/java/org/apache/jackrabbit/webdav/client/methods/BaseDavRequest.java)
> leverages Apache HTTP Components classes (most prominently extends
> {{org.apache.http.client.methods.HttpEntityEnclosingRequestBase}}).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
