[ https://issues.apache.org/jira/browse/HIVE-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242574#comment-15242574 ]
Siddharth Seth commented on HIVE-13490: --------------------------------------- Thanks for the pointer [~ashutoshc]. From the thread, I'm still a little unclear on why we don't want to link the two projects. Is it to avoid a long test run if someone accidentally runs a mvn test ? Don't really see too much more interest here, but I'd imagine this is useful for Hive developers (at least new ones). I'm guessing everyone has their existing workflows to modify itests which work for them. > 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)