hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Kimball (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6503) contrib projects should pull in the ivy-fetched libs from the root project
Date Fri, 22 Jan 2010 21:22:21 GMT

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

Aaron Kimball commented on HADOOP-6503:
---------------------------------------

Todd,

Could you check whether this issue reproduces on trunk and whether this patch fixes it? The
patch looks reasonable -- I think it might need to be applied on trunk and not just 20.

We can always remove redundant ivy dependencies from individual contrib modules later. (Possibly
this should be done on a per-contrib basis by the individual contrib module authors?)

> contrib projects should pull in the ivy-fetched libs from the root project
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-6503
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6503
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.20.1
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hadoop-6503-branch-0.20.txt
>
>
> On branch-20 currently, I get an error just running "ant contrib -Dtestcase=TestHdfsProxy".
In a full "ant test" build sometimes this doesn't appear to be an issue. The problem is that
the contrib projects don't automatically pull in the dependencies of the "Hadoop" ivy project.
Thus, they each have to declare all of the common dependencies like commons-cli, etc. Some
are missing and this causes test failures.

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


Mime
View raw message