Setup publishing to maven-central.

Review Request #2068 - Created April 12, 2015 and submitted

John Sirois
1361, 1409
areitz, benjyw, dturner-tw, stuhood, Yasumoto, zundel
This gets all the pieces in-place to publish pants jvm artifacts to
maven central.  There are currently 2 warts:

 1. The pgp signing requires a passphrase for your key and this is read
    from a properties file in your home dir.  Although this can be setup
    as securely as the ~/.netrc we rely on for maven-central credentials,
    its another file permission someone can get wrong.  I've filed
    tracking issue:
 2. The pre-commit hook gets confused by the automated commits of pushdb
    files and isort checks erroneously fail.  I've not figured the cause
    of the failure yet and have just un-installed my hook for now.
    I've filed tracking issue:

 build-support/ivy/BUILD.netrc                                      |  8 ++++++++
 build-support/ivy/ivy.xml                                          | 20 ++++++++++++++++++++
 build-support/ivy/ivysettings.xml                                  |  2 --
 build-support/ivy/publish.ivysettings.xml                          | 44 ++++++++++++++++++++++++++++++++++++++++++++
 pants-plugins/src/python/internal_backend/repositories/ | 12 ++++++------
 pants.ini                                                          | 18 ++++++++++++++++++
 6 files changed, 96 insertions(+), 8 deletions(-)
I did several publishes from my branch to test this out, but I dropped
the staging repo each time.  This will take some experimentation on
master to sort through any remaining issue that pop up, but things look
good mod the open question of whether the ivy integration will close the
staging repo automatically.

CI went green here:
John Sirois
Eric Ayers
John Sirois
John Sirois
John Sirois
Review request changed

Status: Closed (submitted)