[
https://issues.apache.org/jira/browse/HADOOP-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113884#comment-14113884
]
Hadoop QA commented on HADOOP-11013:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12664993/HADOOP-11013-01.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4568//console
This message is automatically generated.
> CLASSPATH handling should be consolidated, debuggable
> -----------------------------------------------------
>
> Key: HADOOP-11013
> URL: https://issues.apache.org/jira/browse/HADOOP-11013
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Attachments: HADOOP-11013-01.patch, HADOOP-11013.patch
>
>
> As part of HADOOP-9902, java execution across many different shell bits were
> consolidated down to (effectively) two routines. Prior to calling those two
> routines, the CLASSPATH is exported. This export should really be getting
> handled in the exec function and not in the individual shell bits.
> Additionally, it would be good if there was:
> {code}
> echo ${CLASSPATH} > /dev/null
> {code}
> so that bash -x would show the content of the classpath or even a '--debug
> classpath' option that would echo the classpath to the screen prior to java
> exec to help with debugging.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
