Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 12 Sep 2014 20:55:33 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12741167.1410555202000.22821.1410555333774@Atlassian.JIRA>
In-Reply-To: <JIRA.12741167.1410555202000@Atlassian.JIRA>
References: <JIRA.12741167.1410555202000@Atlassian.JIRA>
 <JIRA.12741167.1410555202575@arcas>
Subject: [jira] [Updated] (YARN-2549) TestContainerLaunch fails due to
 classpath problem with hamcrest classes.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth updated YARN-2549:
--------------------------------
    Attachment: YARN-2549.1.patch

Here is a simple pom.xml fix to guarantee that junit (and its hamcrest-core dependency) get on the classpath ahead of mockito.

> TestContainerLaunch fails due to classpath problem with hamcrest classes.
> -------------------------------------------------------------------------
>
>                 Key: YARN-2549
>                 URL: https://issues.apache.org/jira/browse/YARN-2549
>             Project: Hadoop YARN
>          Issue Type: Test
>          Components: nodemanager, test
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>         Attachments: YARN-2549.1.patch
>
>
> The mockito jar bundles its own copy of the hamcrest classes, and it's ahead of our hamcrest dependency jar on the test classpath for hadoop-yarn-server-nodemanager.  Unfortunately, the version bundled in mockito doesn't match the version we need, so it's missing the {{CoreMatchers#containsString}} method.  This causes the tests to fail with {{NoSuchMethodError}} on Windows.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)