[
https://issues.apache.org/jira/browse/LUCENE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603003#comment-16603003
]
David Smiley commented on LUCENE-6259:
--------------------------------------
I'm glad to see there's overall consensus, but this didn't go anywhere. What's
the bare minimum amount of work to do? I'm guessing that would be a build step
to automatically generate one "dependencies.txt" file (a text file of URLs). I
could do this step for Lucene 8.
> Remove dependencies from binary releases
> ----------------------------------------
>
> Key: LUCENE-6259
> URL: https://issues.apache.org/jira/browse/LUCENE-6259
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Ryan Ernst
> Priority: Major
> Attachments: Fetch.java, dependencies.txt
>
>
> In LUCENE-6247, one idea discussed to decrease the size of release artifacts
> was to remove the inclusion of dependencies from binary releases. These jar
> files increase the size of the binary releases a lot, and the size is mostly
> in a couple modules (eg benchmark and spatial).
> I think most people consume lucene through maven. For those that do use the
> binary release, we can still make pulling the dependencies for these modules
> easy. We can add a generated README file in each module that has
> dependencies, with instructions indicating they need to download the
> dependencies, and then give the list of jar files they need to download, with
> exact links to maven (which we can extract from ivy?).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
