[
https://issues.apache.org/jira/browse/LUCENE-10461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505382#comment-17505382
]
Tomoko Uchida commented on LUCENE-10461:
----------------------------------------
I'm now wondering if it is really good for us to keep using `javaw` for Windows
start scripts. I know Window applications should use `javaw` as a general rule
not to block the console, but the plain `java` command should also work well
and it's test-friendly. Another reason I'd like to go back to using `java` is,
it is pretty easy to investigate the problem from the printed console logs when
the launch script fails to start for various reasons (e.g., wrong java home);
meanwhile `javaw` silently exits without any error logs so it's hard to figure
out what went wrong, though I imagine it should be possible to find logs from
system logs.
I'm going to try to switch `java` from `javaw`, but please let me know if there
are good reasons to keep it as is.
> Luke: Windows launch script passes integration tests but fails to run
> ---------------------------------------------------------------------
>
> Key: LUCENE-10461
> URL: https://issues.apache.org/jira/browse/LUCENE-10461
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Major
> Fix For: 9.1, 10.0 (main)
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> PR at https://github.com/apache/lucene/pull/743
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
