You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2009/12/10 04:17:21 UTC
[jira] Assigned: (HDFS-825) Build fails to pull latest
hadoop-core-* artifacts
[ https://issues.apache.org/jira/browse/HDFS-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Boudnik reassigned HDFS-825:
---------------------------------------
Assignee: Konstantin Boudnik
> Build fails to pull latest hadoop-core-* artifacts
> --------------------------------------------------
>
> Key: HDFS-825
> URL: https://issues.apache.org/jira/browse/HDFS-825
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: build
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Priority: Critical
>
> I've noticed on more than one occasion that Ivy cache has staled Common SNAPSHOT jar files. In some cases I've seen more than a month old files. In fact, some very bad problems weren't tested at all, because changes in Common weren't pulled into, say, HDFS where the tests had to be executed.
> I've noticed the same problem with MapReduce just today: latest cached snapshot of Common was a week old.
> One can run clean ivy cache to make sure that latest versions are pulled down. However, it's inconvenient and undesirable to do every time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.