commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siegfried Goeschl (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (EXEC-31) Fix handling of empty environment for forked process
Date Tue, 18 Nov 2008 14:03:44 GMT

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

Siegfried Goeschl resolved EXEC-31.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0

Applied the changes to SVN and fixed the broken test case and it will be part of 1.0

> Fix handling of empty environment for forked process
> ----------------------------------------------------
>
>                 Key: EXEC-31
>                 URL: https://issues.apache.org/jira/browse/EXEC-31
>             Project: Commons Exec
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: Benjamin Bentmann
>            Assignee: Siegfried Goeschl
>            Priority: Minor
>             Fix For: 1.0
>
>         Attachments: EXEC-31.patch
>
>
> The current implementation of {{EnvironmentUtil.toStrings()}} will turn an empty map
into a null array. The {{CommandLauncher}} implementations will then pass this array to {{Runtime.exec()}}.
However, passing in {{null}} for the env argument means to inherit the enviroment, this is
not the same as using an empty environment as specified by the caller. In other words, the
semantics of a null map and an empty map clash which I believe shouldn't.
> I suggest to have {{EnviromentUtils.toStrings()}}
> - output an emtpy array upon input of an empty map
> - output {{null}} upon input of {{null}} (primarily to ease usage, e.g. in the {{CommandLauncher}}'s)

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


Mime
View raw message