[
https://issues.apache.org/jira/browse/HIVE-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294894#comment-13294894
]
Kevin Wilfong commented on HIVE-3092:
-------------------------------------
Carl, do you happen to know why these Hive artifacts are going into Ivy's cache
in the first place? If we could remove them from there, or at least find some
other way to ignore them, that would solve the problems as well.
Having multiple checkouts of Hive store these jars in a common location and
then use them makes it very difficult to work in multiple checkouts at the same
time. It also complicates testing multiple checkouts at the same time.
Given that there isn't a patch for HIVE-3116 yet, I'd like to get this in, to
help speed up development. Having to run ant very-clean package which takes
~20 mins. every time you make a change is a real time sink.
> Hive tests should load Hive classes from build directory, not Ivy cache
> -----------------------------------------------------------------------
>
> Key: HIVE-3092
> URL: https://issues.apache.org/jira/browse/HIVE-3092
> Project: Hive
> Issue Type: Bug
> Components: Testing Infrastructure, Tests
> Reporter: Jakob Homan
> Assignee: Kevin Wilfong
> Attachments: HIVE-3092.1.patch.txt
>
>
> As discussed in HIVE-895, currently the tests pull in jars for other
> components rather from Ivy rather than using the built classes and jars in
> the build directory (bit.ly/LzndQU). This means that absent a very-clean,
> one is testing against a previous version of the code and cross-component
> tests are invalid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
