Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5354#issuecomment-94191765
That sure looks cleaner. Although updating the HTTP client version has some
implications across the code base -- we need to see if we harmonize correctly
on this version and look at the list of changes to decide whether there are
possible conflicts -- I suspect that can be OK and that it helps more than
hurts.
Still on Jackson: is it that you want to standardize on a certain version?
what version? managing the version is a more robust way to do this.
(Reminds me: separately, I should figure out whether we can pull up all of
these messy exclusions into the parent. They shouldn't go in the child POMs.)
Does the new release of Tachyon remove some dependencies? that is, it's
great that almost all the exclusions are gone, but that doesn't mean that this
now brings in more dependencies does it? Jenkins will tell us ---
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
