[
https://issues.apache.org/jira/browse/LUCENE-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173929#comment-17173929
]
Tomoko Uchida commented on LUCENE-9448:
---------------------------------------
Hi [~erickerickson]
as for SOLR-13412, I think there wouldn't be nothing special to ship Luke with
Solr - it's just an ordinary JAR file (like other lucene modules) and its all
dependent jars may be already included in Solr. Once correct class paths are
set, Luke runs on everywhere else. (Please see this launch shell/bat:
[https://github.com/apache/lucene-solr/tree/master/lucene/luke/bin])
I'm not fully sure if it'd be somewhat helpful/useful for Solr users though...
> Make an equivalent 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
> Attachments: LUCENE-9448.patch
>
>
> 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
