[
https://issues.apache.org/jira/browse/LUCENE-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173081#comment-17173081
]
Dawid Weiss commented on LUCENE-9448:
-------------------------------------
> Why would that hang the IDE?
I'm guessing IntelliJ has a single worker gradle daemon.... guessing though.
bq. Luke is not a self-contained jar and the relative location of the dependent
jars are different in building and packaging time, we can't specify build time
Class-Path in the JAR Manifest. (Am I correct?)
They are different but they point at the same set of artifacts. It's really
simple to sync libs and set proper relative manifest based on that. Look at
this snippet, for example:
https://github.com/carrot2/carrot2/blob/master/dcs/distribution/build.gradle#L38-L54
> 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
