hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Peña (JIRA) <j...@apache.org>
Subject [jira] [Commented] (HIVE-13490) Change itests to be part of the main Hive build
Date Fri, 06 May 2016 15:01:12 GMT

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

Sergio Peña commented on HIVE-13490:
------------------------------------

[~kgyrtkirk] Your changes may work great for this :)

I'd like to build itests/ from the root and make it easy for IDE to see it as part of the
project. It's good we can skip these long q-tests from running when executing 'mvn test' from
the root.

I know there is a build phase on maven to execute integration tests with {{mvn verify}}. This
uses the maven failsafe plugin. Do you think we can do something with that plugin that allows
q-test execution from the root directory?

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

Mime
View raw message