Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 11 May 2011 04:15:47 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1741005890.2089.1305087347360.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <21922935.186601292622961312.JavaMail.jira@thor>
Subject: [jira] [Commented] (HADOOP-7068) Ivy resolve force mode should be
 turned off by default
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031530#comment-13031530 ] 

Hudson commented on HADOOP-7068:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #588 (See [https://builds.apache.org/hudson/job/Hadoop-Common-trunk-Commit/588/])
    HADOOP-7068. Ivy resolve force mode should be turned off by default. Contributed by Luke Lu.


> 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