You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@pig.apache.org by "Pradeep Kamath (JIRA)" <ji...@apache.org> on 2010/04/02 01:20:27 UTC

[jira] Updated: (PIG-1346) In unit tests Util.executeShellCommand relies on java commands being in the path and does not consider JAVA_HOME

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

Pradeep Kamath updated PIG-1346:
--------------------------------

    Status: Open  (was: Patch Available)

> In unit tests Util.executeShellCommand relies on java commands being in the path and does not consider JAVA_HOME
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: PIG-1346
>                 URL: https://issues.apache.org/jira/browse/PIG-1346
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.6.0, 0.7.0
>            Reporter: Pradeep Kamath
>            Assignee: Pradeep Kamath
>         Attachments: PIG-1346.patch
>
>
> Util.executeShellCommand is currently used in unit tests to execute java related binaries like "java", "javac", "jar" - this method should check if JAVA_HOME is set and use $JAVA_HOME/bin/java etc. If JAVA_HOME is not set, the method can try and execute the command as-is.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.