Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1397513517.1261107738321.JavaMail.jira@brutus>
Date: Fri, 18 Dec 2009 03:42:18 +0000 (UTC)
From: "Aaron Kimball (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6370) Contrib project ivy dependencies
 are not included in binary target
In-Reply-To: <2115738009.1258057839756.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron Kimball commented on HADOOP-6370:
---------------------------------------

Possibly. It's worth noting that contrib projects also pull in many of the same jars as those used by Hadoop itself. So we'd want to deduplicate from those used by the common project first, or else we'll wind up having a *very* bloated binary tarball. Do you know of a straightforward way to do this?


> Contrib project ivy dependencies are not included in binary target
> ------------------------------------------------------------------
>
>                 Key: HADOOP-6370
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6370
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>            Reporter: Aaron Kimball
>            Assignee: Aaron Kimball
>            Priority: Critical
>         Attachments: HADOOP-6370.patch
>
>
> Only Hadoop's own library dependencies are promoted to ${build.dir}/lib; any libraries required by contribs are not redistributed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.