[
https://issues.apache.org/jira/browse/HADOOP-9935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth resolved HADOOP-9935.
-----------------------------------
Resolution: Fixed
André, sorry I didn't catch the problem at code review time. I frequently use
the {{CreateEditsLog}} tool, so I should have thought to test that.
bq. Why isn't the tests jar a "hadoop compliant jar", that includes junit, like
any other hadoop app? Is there a reason, to treat it special?
The current situation isn't ideal, but it appears that we need to keep it this
way for backwards-compatibility right now. Thanks to Jason for pointing out
HADOOP-8738 and HADOOP-9116, which will address the root cause. André, perhaps
you'd like to participate on those other 2 issues.
I'm resolving this as a duplicate of HADOOP-8738.
> set junit dependency to test scope
> ----------------------------------
>
> Key: HADOOP-9935
> URL: https://issues.apache.org/jira/browse/HADOOP-9935
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, test
> Affects Versions: 2.1.0-beta
> Reporter: André Kelpe
> Assignee: André Kelpe
> Fix For: 3.0.0, 2.1.1-beta
>
> Attachments: HADOOP-9935.patch, HADOOP-9935.patch
>
>
> junit should be set to scope test in hadoop-mapreduce-project and
> hadoop-yarn-project. This patch will fix the problem, that hadoop always
> pulls in its own version of junit and that junit is even included in the
> tarballs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
