On 13/02/13 20:53, Stephen Allen wrote:
All,
I'm trying to sort out some discrepancies in the httpclient
dependencies in ARQ and Fuseki. Basically I'm wondering why specific
versions of httpcore and commons-codec are specified.
httpclient:4.2.3 depends on httpcore:4.2.2 and commons-codec:1.6 (the
dependency on the previous version of httpcore is pretty odd).
However, ARQ itself directly depends on httpcore:4.2.3 and
commons-codec:1.5, which means they override the transitive
dependencies specified by httpclient. Is there a reason for these
different versions? If no, then we should probably eliminate the
direct dependencies and if no, we should explicitly exclude the
transitive dependencies.
I am going to take the first approach of eliminating the direct
dependencies (and thus reverting to httpcore:4.2.2). Let me know if
this is not good or if we really need httpcore:4.2.3 and I'll go the
other route. The other thing I'm going to do is turn on the enforcer
plugin to run for every compile, so hopefully it'll help keep our
dependencies kosher in the future.
-Stephen
Looks good. Seems easiest to just depend in ARQ in httpclient and the
version in jena-parent. Fuseki needs httpclient because of the
datasetaccessor code which is in the wrong place but moving is a package
rename.
We could move it in time for Jena 2.10.0 and then (and I haven't
checked) Fuseki does not need httpclient although it will get it via ARQ
anyway.
If we need later httpcore (and I think it was just a general update
thing) we can also put a version for httpcore in parent.
commons-codec can just fall out in the wash nowadays. I think it was
added first.
Andy
