[jira] [Updated] (HIVE-2559) Add target to install Hive JARs/POMs in the local Maven cache

["Alan Gates (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Gates updated HIVE-2559:
-----------------------------

    Attachment: HIVE-2559.patch

Addition to build.xml to allow publishing to local maven repo.  With this if you do:

{code}
ant package
ant -Dmvn.publish.repo=local maven-build
ant -Dmvn.publish.repo=local maven-publish
{code}

You'll publish the jars to your local maven repo (by default located in ~/.m2).

Note that you must do an "ant package" first because the jar target (which maven-build depends on) doesn't build the builtins.  This looked like a bug, but I didn't change it because the maven-build target is part of the nightly build and release publishing process, and I did not want to mess it up.

Could someone with appropriate power assign this JIRA to me?  Or better yet put me in the contributor list so I can assign it to myself.  Thanks.

                
> Add target to install Hive JARs/POMs in the local Maven cache
> -------------------------------------------------------------
>
>                 Key: HIVE-2559
>                 URL: https://issues.apache.org/jira/browse/HIVE-2559
>             Project: Hive
>          Issue Type: Improvement
>          Components: Build Infrastructure
>    Affects Versions: 0.9.0
>            Reporter: Alejandro Abdelnur
>            Priority: Critical
>         Attachments: HIVE-2559.patch
>
>
> HIVE-2391 is producing usable Maven artifacts.
> However, it only as a target to deploy/publish those artifacts to Apache Maven repos.
> There should be a new target to locally install Hive Maven artifacts, thus enabling their use from other projects before they are committed/publish to Apache Maven (this is critical to test patches that may address issues in downstream components).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira