[
https://issues.apache.org/jira/browse/LUCENE-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175661#comment-17175661
]
Tomoko Uchida commented on LUCENE-9448:
---------------------------------------
Thank you [~dweiss] for your help.
{quote}luke's build file declares an exportable configuration 'standalone' that
includes a set of preassembled dependencies and classpath-enriched Luke JAR.
This configuration is separate from the default project JAR. It can be
assembled (standaloneAssemble), compressed into a tgz archive
(standalonePackage) or exported and reused elsewhere
{quote}
As for 'standalone' package, there are drop-in runtime only dependencies (many
analysis modules) which are not required for development at all. If we make
complete standalone distribution package by Gradle script, we need to collect
all such jars or add all of them to compile time dependencies.
I'll try it a little later (have little time right now).
> 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, 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
