Robustify the pants ivy configuration.
Review Request #2450 - Created July 9, 2015 and submitted
|benjyw, stuhood, zundel|
This turns on required pom downloads from maven-central for atrifact resolves to be considered successful. It also enables the jakarta commons http-client for downloads which has the effect of enabling retries leading to less transient resolve failures. Inspired by investigatory/expository work in: https://github.com/pantsbuild/pants/issues/1779 build-support/ivy/ivy.xml | 3 +++ build-support/ivy/ivysettings.xml | 12 ++++++------ 2 files changed, 9 insertions(+), 6 deletions(-)
Locally ran:$ rm -rf ~/.ivy2/pants/com.google.guava/ $ ./pants clean-all resolve.ivy --args=-verbose :jar-tool
The pants server console stdout for ivy resolve confirmed jakarta commons
http-client was selected.
CI went green here: