[
https://issues.apache.org/jira/browse/HIVE-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250537#comment-15250537
]
Sergio Peña commented on HIVE-13490:
------------------------------------
I think "itests" should be kept separately from the root project to
differentiate from real 'unit' tests vs 'integration' tests.
Some developers would like to run only unit tests, and they can execute {{mvn
test}} from the root directory. But, with this change, if we run {{mvn test}},
it will execute all "itests" as well, and this can run for hours.
Sorry, but I'll have to do a -1 until we decide what's better. Btw, I like your
idea to manage IntelliJ, but I'm afraid this will cause others people testing
infra to run more time.
> 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)
