Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 15 Jun 2012 12:28:43 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <1772741653.18587.1339763323580.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1434249188.43255.1338979164485.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HIVE-3092) Hive tests should load Hive classes
 from build directory, not Ivy cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295623#comment-13295623 ] 

Hudson commented on HIVE-3092:
------------------------------

Integrated in Hive-trunk-h0.21 #1488 (See [https://builds.apache.org/job/Hive-trunk-h0.21/1488/])
    HIVE-3092 Hive tests should load Hive classes from build directory, not Ivy cache
(Kevin Wilfong via namit) (Revision 1350467)

     Result = FAILURE
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1350467
Files : 
* /hive/trunk/build-common.xml

                
> Hive tests should load Hive classes from build directory, not Ivy cache
> -----------------------------------------------------------------------
>
>                 Key: HIVE-3092
>                 URL: https://issues.apache.org/jira/browse/HIVE-3092
>             Project: Hive
>          Issue Type: Bug
>          Components: Testing Infrastructure, Tests
>            Reporter: Jakob Homan
>            Assignee: Kevin Wilfong
>         Attachments: HIVE-3092.1.patch.txt, HIVE-3092.2.patch.txt
>
>
> As discussed in HIVE-895, currently the tests pull in jars for other components rather from Ivy rather than using the built classes and jars in the build directory (bit.ly/LzndQU).  This means that absent a very-clean, one is testing against a previous version of the code and cross-component tests are invalid.

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