[
https://issues.apache.org/jira/browse/OPENNLP-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147605#comment-13147605
]
Aliaksandr Autayeu commented on OPENNLP-361:
--------------------------------------------
It is a good idea about short path names! Thank you. It might be also a good
idea to do the same with OPENNLP_HOME. If it is not set by the user, it is fine
thanks to %~sp0.. in the bat. But if it is set by the user and it contains
spaces... then it does not work again :) Easier alternative to all these
troubles might be to write in the bat that OPENNLP_HOME should not contain
spaces :)
It might be also a good idea to use SETLOCAL ... ENDLOCAL around the script, to
avoid interfering with other scripts, which might use JAVA_CMD.
Anyway, I have tested the new .bat, it does work with my command-line scripts.
> handling spaces in JAVA_HOME
> ----------------------------
>
> Key: OPENNLP-361
> URL: https://issues.apache.org/jira/browse/OPENNLP-361
> Project: OpenNLP
> Issue Type: Bug
> Components: Command Line Interface
> Affects Versions: tools-1.5.3-incubating
> Environment: Windows 7
> Reporter: Aliaksandr Autayeu
> Assignee: James Kosin
> Labels: patch
> Fix For: tools-1.5.3-incubating
>
> Attachments: 0001-handling-spaces-in-JAVA_HOME.patch,
> 0007-handling-spaces-in-JAVA_HOME-quote-on-use-for-succes.patch
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> If JAVA_HOME contains spaces, opennlp.bat fails to execute java.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
