Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 90DE29DDD for ; Fri, 1 Jun 2012 21:25:27 +0000 (UTC) Received: (qmail 87167 invoked by uid 500); 1 Jun 2012 21:25:24 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 87086 invoked by uid 500); 1 Jun 2012 21:25:24 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 86773 invoked by uid 99); 1 Jun 2012 21:25:24 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2012 21:25:24 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 7516E1400E2 for ; Fri, 1 Jun 2012 21:25:24 +0000 (UTC) Date: Fri, 1 Jun 2012 21:25:24 +0000 (UTC) From: =?utf-8?Q?Bruno_Mah=C3=A9_=28JIRA=29?= To: common-issues@hadoop.apache.org Message-ID: <43167753.28336.1338585924484.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Created] (HADOOP-8466) hadoop-client POM incorrectly excludes avro MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Bruno Mah=C3=A9 created HADOOP-8466: ---------------------------------- Summary: hadoop-client POM incorrectly excludes avro Key: HADOOP-8466 URL: https://issues.apache.org/jira/browse/HADOOP-8466 Project: Hadoop Common Issue Type: Bug Components: build Affects Versions: 2.0.0-alpha Reporter: Bruno Mah=C3=A9 Assignee: Bruno Mah=C3=A9 avro is used by Serializers initialization, thus it must be there -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp= a For more information on JIRA, see: http://www.atlassian.com/software/jira