[
https://issues.apache.org/jira/browse/LUCENE-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173034#comment-17173034
]
Dawid Weiss commented on LUCENE-9448:
-------------------------------------
Hmm... This would keep the gradle daemon running while the subprocess is
launched.
My opinion is that it makes little sense, to be honest. Rather, the assembly
should be straightened up so that build/luke contains the scripts and
dependencies required to run Luke. Then you could do:
gradlew :lucene:luke:assemble
and it'd compile everything needed, then maybe print something like:
Luke is ready to launch, run it with:
java -jar lucene/luke/build/luke/luke....jar
A proper classpath manifest and main class would be also helpful (then you
don't have to run any scripts, just the jar itself).
> Make an eqivalent to Ant's "run" target for Luke module
> -------------------------------------------------------
>
> Key: LUCENE-9448
> URL: https://issues.apache.org/jira/browse/LUCENE-9448
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Tomoko Uchida
> Priority: Minor
>
> With Ant build, Luke Swing app can be launched by "ant run" after checking
> out the source code. "ant run" allows developers to immediately see the
> effects of UI changes without creating the whole zip/tgz package (originally,
> it was suggested when integrating Luke to Lucene).
> In Gradle, {{:lucene:luke:run}} task would be easily implemented with
> {{JavaExec}}, I think.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
