Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 20 Sep 2011 00:21:09 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <439040625.44379.1316478069059.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1881607754.61519.1302909605732.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HADOOP-7228) jar names are not compatible with
 0.20.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Allen Wittenauer resolved HADOOP-7228.
--------------------------------------

    Resolution: Won't Fix

Surprise.

> jar names are not compatible with 0.20.2
> ----------------------------------------
>
>                 Key: HADOOP-7228
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7228
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 0.20.203.0
>            Reporter: Allen Wittenauer
>            Priority: Critical
>
> The jars in 203 are named differently vs. Apache Hadoop 0.20.2.  I understand this was done to make the Maven people less cranky.  However, this breaks compatibility especially for streaming users. We need to make sure we have a release note or something significant so that users aren't taken by surprise.

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