hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuefu Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-12984) spark tgz-s need to be deleted on mvn clean, as are other binary artifacts in the tree
Date Tue, 02 Feb 2016 20:57:39 GMT

    [ https://issues.apache.org/jira/browse/HIVE-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15129012#comment-15129012
] 

Xuefu Zhang commented on HIVE-12984:
------------------------------------

[~sershe], that would be indeed a pain for developers. It takes a while to download. I'm not
sure why excluding it from src.xml wouldn't work. Also, when I build with -Pdist, I don't
see thirdparty directory in the package.

> spark tgz-s need to be deleted on mvn clean, as are other binary artifacts in the tree
> --------------------------------------------------------------------------------------
>
>                 Key: HIVE-12984
>                 URL: https://issues.apache.org/jira/browse/HIVE-12984
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-12984.patch
>
>
> Currently, tgz files are downloaded and kept around forever. I noticed when packaging
the release (apparently the excludes in packaging files also didn't work) that the initial
src tar.gz was huge; regardless of that, I had 6 version of spark (1.2 thru 1.6 with one dot
version) sitting there, and also in every clone of Hive that I have.
> These should be switched to use normal means of artifact distribution (I think I already
filed a jira but I cannot find it now); meanwhile making sure that mvn clean would remove
them.
> I realize it could create some pain when running tests repeatedly on dev machine unless
"clean" is omitted from rebuilds; that is somewhat intentional - it should be a good incentive
to switch to maven for dependency management instead of a bash script ;)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message