[
https://issues.apache.org/jira/browse/TIKA-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386922#comment-14386922
]
Hudson commented on TIKA-1587:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.7 #586 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/586/])
Fix broken ForkParser APIs
Fixes TIKA-1587 (grossws:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1670125)
* /tika/trunk/tika-core/src/main/java/org/apache/tika/fork/ForkParser.java
> 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)
