hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-7068) Ivy resolve force mode should be turned off by default
Date Wed, 11 May 2011 03:59:50 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tom White updated HADOOP-7068:

       Resolution: Fixed
    Fix Version/s: 0.22.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

I've just committed this. Thanks, Luke!

> Ivy resolve force mode should be turned off by default
> ------------------------------------------------------
>                 Key: HADOOP-7068
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7068
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Luke Lu
>            Assignee: Luke Lu
>             Fix For: 0.22.0
>         Attachments: hadoop-7068-trunk-v1.patch, hadoop-7068-trunk-v2.patch
> The problem is introduced by  HADOOP-6486. Which have caused a lot of mysterious artifact
issues (unable to downgrade or do parallel dev, without wiping out both m2 and ivy caches
etc.) wasting countless hours of dev (many people's) time to track down the issue.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message