[
https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571959#comment-15571959
]
ASF GitHub Bot commented on JENA-576:
-------------------------------------
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/151
Holy moly, @afs , thanks for the huge assist! I was out yesterday (Yom
Kippur) and am now catching up. I will leave comments specific to the HTTP
question on the new PR, but I will try to speak to the other points here.
1. I am certainly happy to see a spurious plugin go. I have no problem with
including that change in this package of changes, if that's okay with everyone
else. Or it could be a quick separate ticket/commit, to keep thing straighter
in the history.
2. I have no idea why `maven-source-plugin ` is overridden. Baggage from
long-ago when this material was imported into the main code base?
3. I haven't seen AspectJ used anywhere, but I haven't been all through the
`jdbc` code. Same as the first point-- I have no problem removing it here or
elsewhere.
> 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)
