[jira] [Commented] (HIVE-13490) Change itests to be part of the main Hive build

["Zoltan Haindrich (JIRA)" <ji...@apache.org>]

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

Zoltan Haindrich commented on HIVE-13490:
-----------------------------------------

I've also attached the itests to my top level project; and i've played a lot with eclipse to be able to execute most of the unit tests directly from eclipse ; plus the qtests...I'm glad that it works now ;)
But it's not very easy to set it up...i've uncovered a few things - which could be addressed programatically, or by using some conventions:
 * there are a few path related properties (${test.data.files} and friends) which could be defaulted to some path if the project root is known - the project root can be detected by a few simple checks (for example existence of the {{ql}} directory...or anything special) - I would definetly keep the finer grained properties - but they wouldn't be mandatory anymore
 * every test execution gets it's hive configuration xmls thru an extra classpath entry supplied by the maven surefire plugin - if the configuration could be kept in a unique directory - it could be loaded more precisely without problems for the ide.
 * i'm not a maven expert but it might be possible to mask the itests / test task by using some kind of profile - this might prevent {{mvn test}} from recklessly executing integration tests by default

are there any intrest in these?

> Change itests to be part of the main Hive build
> -----------------------------------------------
>
>                 Key: HIVE-13490
>                 URL: https://issues.apache.org/jira/browse/HIVE-13490
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: HIVE-13490.01.patch, HIVE-13490.02.patch
>
>
> Instead of having to build Hive, and then itests separately.
> With IntelliJ, this ends up being loaded as two separate dependencies, and there's a lot of hops involved to make changes.
> Does anyone know why these have been kept separate ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)