[
https://issues.apache.org/jira/browse/HADOOP-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806044#action_12806044
]
Todd Lipcon commented on HADOOP-6503:
-------------------------------------
This doesn't seem to reproduce on trunk, at least with hdfsproxy - I think it's
because trunk has been somewhat mavenified. The dependency that ivy.xml
specifies on hadoop-core probably pulls in the transitive dependencies. I
tested by removing the explicit commons-cli dependency from
src/contrib/hdfsproxy/ivy.xml and the test still passed.
Given this, the ivy.xml for the contrib projects can probably be pared down a
bit, but I agree with Aaron we should probably leave it up to those authors if
it's not causing problems for the overall build.
> 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.
