[
https://issues.apache.org/jira/browse/HDFS-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788929#action_12788929
]
Konstantin Boudnik commented on HDFS-825:
-----------------------------------------
Here's a link to the Ivy's documentation which tell about metadata
modifications:
http://ant.apache.org/ivy/history/trunk/concept.html
Look under
Cache and Change Management
Change management
"Changes in module metadata" and "Changes in artifacts"
Hope it helps.
> 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: 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.
