[
https://issues.apache.org/jira/browse/HIVE-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277144#comment-15277144
]
Zoltan Haindrich commented on HIVE-13490:
-----------------------------------------
[~spena]: i've looked around a bit, what could be done to enable failsafe - if
the integrations test would follow some integration test naming scheme, then it
might be possible...or in the current setup it might be possible to disable
surefire's inclusion inside itests; and add them to failsafe's in the mean time.
but i think there is a bigger problem, which obstructs this change: ...(AFAIK)
adding failsafe to the project would also need to duplicate all the
customization done for surefire in /pom.xml and add them for failsafe
too...this might give rise for errors from this dupication later.
I think it would be better to minimize the extra external configuration tweeks
done at the maven level prior to test execution; these properties and classpath
settings are not seen by the IDE, and it's very complicated to set them up to
be able to execute them....
i would recommend to add failsafe later; after convinient ide test execution is
available.
> 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)
