hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-825) Build fails to pull latest hadoop-core-* artifacts
Date Mon, 14 Dec 2009 23:41:18 GMT

    [ https://issues.apache.org/jira/browse/HDFS-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790457#action_12790457

Hudson commented on HDFS-825:

Integrated in Hadoop-Hdfs-trunk-Commit #145 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/145/])
    . Build fails to pull latest hadoop-core-* artifacts. Contributed by 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
>         Attachments: HDFS-825.patch, latest-mod-check.patch
> 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.

View raw message