[
https://issues.apache.org/jira/browse/HIVE-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297156#comment-15297156
]
Siddharth Seth commented on HIVE-13490:
---------------------------------------
[~kgyrtkirk] - I'd be in favour of the second approach, which allows the tests
to be run from the top level with a profile, unless there's some downsides to
it ? Will the profile need to be specified within the itest directory as well ?
That would break existing usage scenarios as well.
Please feel free to take over this jira, if you're making this change.
[~spena] - should we look at failsafe in an alternate jira ? Looks like
[~kgyrtkirk] already has an approach identified which builds itest directly,
improved IDE integration and avoids running the itests when invoking mvn test
from the top level.
> 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)
