[
https://issues.apache.org/jira/browse/HIVE-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth updated HIVE-13490:
----------------------------------
Attachment: HIVE-13490.01.patch
Turns out to be a very simple patch - include itests in the modules list in the
top level pom.
Verified that the artifacts generated by mvn package are the same with and
without the patch.
Also, a mvn import into IntelliJ works a lot better now.
I'm not sure this needs hive-qa to run. We could change some of the commands
which are run by HiveQA after this goes in (separate builds for hive and itests
not required).
Would be good if folks can try this out with the IDEs they use. See if the
imports work as they should. I've tried intellij.
cc [~ashutoshc], [~thejas]
> 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
>
>
> 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)
