[
https://issues.apache.org/jira/browse/LUCENE-9978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436440#comment-17436440
]
ASF subversion and git services commented on LUCENE-9978:
---------------------------------------------------------
Commit 627ef4d469975044cce21fcfcf08ed65afbe7e0d in lucene's branch
refs/heads/main from Dawid Weiss
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=627ef4d ]
LUCENE-9978: Integrate Luke with the binary release package.
> Make Luke a standalone package distribution
> -------------------------------------------
>
> Key: LUCENE-9978
> URL: https://issues.apache.org/jira/browse/LUCENE-9978
> Project: Lucene - Core
> Issue Type: Task
> Affects Versions: main (9.0)
> Reporter: Tomoko Uchida
> Priority: Major
>
> Thanks to LUCENE-9448, we now have a neat gradle task to assemble a
> standalone Luke package.
> I think it would make sense to distribute the standalone "Luke application"
> that contains its executable-jar and minimum dependencies to run it, as it
> used to be, on Lucene download page (
> [https://lucene.apache.org/core/downloads.html] ).
> Pros:
> - Easy to understand for users who need it
> - No need to rely on strange hacks to discover dependencies (jars) for
> running it
> Cons:
> - Duplication of many jars (analyzers, queries, codec, etc.)
>
> Tasks
> * make the distribution package (zip file); place it under proper location
> with gradle assemble task
> * upload the artifact (release candidate) to the Apache file server along
> with other Lucene artifacts
> * include the artifact url in the release vote emails
> * upload the artifact (release module) to the Apache file server along with
> signature/checksum files for it
> * put links to the artifact and its signature files on the Lucene download
> page
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
