hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9935) set junit dependency to test scope
Date Fri, 06 Sep 2013 15:26:52 GMT

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

Steve Loughran commented on HADOOP-9935:

one diff for the mapreduce/ bit of the source tree, one diff for the hadoop-yarn section,
submitted as bugs against yarn and mapreduce projects , with the "submit patch" button set
to trigger the relevant build and test.

When I apply the patch -which I will do- I will do the unified patch, as that will mean only
one patch backport from trunk -it's just that we want jenkins to do the work.

Actually, you could just get away with creating JIRAs for the two things and submitting the
same patch to all. Let me try that
> set junit dependency to test scope
> ----------------------------------
>                 Key: HADOOP-9935
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9935
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.1.0-beta
>            Reporter: André Kelpe
>         Attachments: 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

View raw message