You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2013/03/05 00:53:13 UTC
[jira] [Updated] (YARN-449) MRAppMaster classpath not set properly
for unit tests in downstream projects
[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Seth updated YARN-449:
--------------------------------
Summary: MRAppMaster classpath not set properly for unit tests in downstream projects (was: MRAppMaster not set properly for unit tests in downstream projects)
> MRAppMaster classpath not set properly for unit tests in downstream projects
> ----------------------------------------------------------------------------
>
> Key: YARN-449
> URL: https://issues.apache.org/jira/browse/YARN-449
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.0.3-alpha
> Reporter: Siddharth Seth
> Priority: Blocker
>
> Post YARN-429, unit tests for HBase continue to fail since the classpath for the MRAppMaster is not being set correctly.
> Reverting YARN-129 may fix this, but I'm not sure that's the correct solution. My guess is, as Alexandro pointed out in YARN-129, maven classloader magic is messing up java.class.path.
--
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