[
https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575501#comment-15575501
]
ASF GitHub Bot commented on JENA-576:
-------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/151
http_op_3 branch should be good now : ServerCtl moved to fuseki1 and used
uniformly. After this is finished, it coudl be cleaned up or more reasonably,
extract that code, add the capabilities to jena-fuseki2-embedded and change
jena-jdbc-driver-remote accordingly (just imports by that stage?).
Several commits.
If ti works to merge from that branch, they'll be more "git checking"
everything is pulled in.
> Upgrade Apache HTTP Client to 4.3
> ---------------------------------
>
> Key: JENA-576
> URL: https://issues.apache.org/jira/browse/JENA-576
> Project: Apache Jena
> Issue Type: Dependency upgrade
> Components: ARQ
> Affects Versions: Jena 2.11.0
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Priority: Minor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> As of 2.11.0 ARQ centralizes all HTTP operations through HttpOp which relies
> on Apache HTTP Client. Currently we are using 4.2.3 while the latest stable
> release is actually 4.3.1
> Therefore we should look at upgrading our code to use the latest version
> which may entail some refactoring since there appears to have been some
> breaking changes across the minor version bump which users have seen in usage
> - e.g.
> https://github.com/pyvandenbussche/sparqles/issues/9#issuecomment-27220738
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
