Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail From: =?ISO-8859-1?Q?Sven_K=F6hler?= Newsgroups: comp.lang.java.programmer Subject: Re: exec problem is JDK 1.7.0_21 Date: Sun, 28 Apr 2013 10:57:37 +0300 Lines: 19 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.dfncis.de q44wRWy3mxPeHhP45BBpbAR0z226n3Hahwq/w6L9b2mFdPAVQOA3U6OOHY Cancel-Lock: sha1:R2cb6HxePm5Q3nbgm9o78vPSAAM= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:23688 On 04/26/2013 12:38 AM, Arved Sandstrom wrote: > My comment just meant what it said - identify the specific app on > Windows, the arguments it needs, and do what you need to do with > ProcessBuilder - in a way irrespective of official docs - to make it work. OK, I've done that. In my case, it is possible to workaround the buggy ProcessBuilder escaping - luckily. Now, in other cases it's actually impossible, as ProcessBuilder will add quotes where they don't belong. For the sake of argument, let's assume my case would be of the latter type: I can't workaround ProcessBuilder's mangling of Strings. What do I do now? And why does this matter for the question, whether ProcessBuilder is broken or not? Regards, Sven