Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 15 Dec 2011 20:15:32 +0000 (UTC)
From: "Phabricator (Updated) (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: 
 <485169804.16860.1323980132389.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <433929640.16293.1323970591156.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HIVE-2657) builtins JAR is not being published to
 Maven repo & hive-cli POM does not depend on it either
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Phabricator updated HIVE-2657:
------------------------------

    Attachment: HIVE-2657.D897.1.patch

cwsteinbach requested code review of "HIVE-2657 [jira] builtins JAR is not being published to Maven repo & hive-cli POM does not depend on it either".
Reviewers: JIRA

  Make hive-cli and hive-ql depend on hive-builtins

TEST PLAN
  EMPTY

REVISION DETAIL
  https://reviews.facebook.net/D897

AFFECTED FILES
  cli/ivy.xml
  ql/ivy.xml

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/1887/

Tip: use the X-Herald-Rules header to filter Herald messages in your client.

                
> builtins JAR is not being published to Maven repo & hive-cli POM does not depend on it either
> ---------------------------------------------------------------------------------------------
>
>                 Key: HIVE-2657
>                 URL: https://issues.apache.org/jira/browse/HIVE-2657
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.9.0
>            Reporter: Alejandro Abdelnur
>             Fix For: 0.9.0
>
>         Attachments: HIVE-2657.D897.1.patch
>
>


--
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