[
https://issues.apache.org/jira/browse/HDFS-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated HDFS-825:
------------------------------------
Attachment: HDFS-825.patch
I've ended up using {{chackmodified}} and {{changingPattern}} with an actual
pattern for the latter. I think Ivy documentation is pretty fuzzy in this
respect.
I've verified the patch on my home machine for Hdfs workspace and will verify
it tomorrow with another box where I have an MR workspace with stale jar files
in the Ivy cache.
> 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
> 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.
