[
https://issues.apache.org/jira/browse/LUCENE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327608#comment-14327608
]
Mark Miller commented on LUCENE-6259:
-------------------------------------
bq. I think we should just provide a list of URLs
Yeah, I agree that is probably enough, especially to get something done now,
but it wouldn't hurt if someone wanted to go through the effort to have some
readable format and an optional 'java -jar get.jar deps.txt' possible on top of
it. For people that are not consuming this from maven, it lessons the user
experience impact to have a single command that can pull in what you need. If
it was complicated, it probably wouldn't be worth maintaining, but seems pretty
simple.
> 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
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
