[
https://issues.apache.org/jira/browse/HIVE-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274131#comment-15274131
]
Zoltan Haindrich commented on HIVE-13490:
-----------------------------------------
i've played with this a bit...I just want to add the itests module
anyhow...without breaking the existing usage pattern.
i don't wanted to pollute this ticket with alternatives...so i used some
pastebin tool
the following maven changes disables the integration test executions if the
'itests' folder exists in the current dirrectory -> cwd==hive.root
http://hastebin.com/omuzuwaboj.xml
with this there is no way to run integration tests from the root project; and
AFAIK there is no way to enable that - but for ide profiles its enough
but there is a positive side of this solution: itests subtree is compiled with
the rest of the project
it would be also possible to enable&use itests using some profile;
positive: from the root directory anyone could use a more sophisticated command
to directly run integration tests {{mvn test -rf itests/qtest -Pitests
-Dtest=TestCliDriver -Dqfile=view.q}}
http://hastebin.com/lukesukuva.xml
> 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)
