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

Posted to dev@tika.apache.org by "Konstantin Gribov (JIRA)" <ji...@apache.org> on 2015/03/30 16:29:53 UTC

[jira] [Resolved] (TIKA-1587) ForkParser::setJavaCommand should take List

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

Konstantin Gribov resolved TIKA-1587.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8
         Assignee: Konstantin Gribov

Sorry, I forgot to include "Fixes ..." in commit message.

> ForkParser::setJavaCommand should take List<String>
> ---------------------------------------------------
>
>                 Key: TIKA-1587
>                 URL: https://issues.apache.org/jira/browse/TIKA-1587
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 1.7
>            Reporter: Oleg Oshmyan
>            Assignee: Konstantin Gribov
>             Fix For: 1.8
>
>         Attachments: TIKA-1587.patch
>
>
> ForkParser::setJavaCommand currently takes a string and splits it on whitespace. This makes it impossible to use commands with paths that contain spaces. In particular, it makes it impossible to reliably use System.getProperty("java.home") in order to launch the same Java that the current process is running in, because it might contain spaces. If it would just take a List<String> and pass (a clone of) it directly to ProcessBuilder, this wouldn't be a problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)