You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2016/02/02 20:48:39 UTC
[jira] [Updated] (HIVE-12984) spark tgz-s need to be deleted on mvn
clean, as are other binary artifacts in the tree
[ https://issues.apache.org/jira/browse/HIVE-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Shelukhin updated HIVE-12984:
------------------------------------
Summary: spark tgz-s need to be deleted on mvn clean, as are other binary artifacts in the tree (was: spark tgz need to be deleted on mvn clean, as are other binary artifacts in the tree)
> 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)