[
https://issues.apache.org/jira/browse/LUCENE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328083#comment-14328083
]
Dawid Weiss commented on LUCENE-6259:
-------------------------------------
I don't know, Ryan, I just wanted to implement that progress indicator so
badly... Idée fixe.
Anyway, more seriously -- I agree with Mark that this should be top-level and
simply fetch libraries in their appropriate locations; don't know if you
noticed the 'saveTo' directive:
{code}
#@saveTo lib/lucene/
http://repo1.maven.org/maven2/org/apache/lucene/lucene-core/4.10.3/lucene-core-4.10.3.jar
http://repo1.maven.org/maven2/org/apache/lucene/lucene-memory/4.10.3/lucene-memory-4.10.3.jar
{code}
If the tools is simple enough then it can be even embedded in one of the JARs
(like other command-line tools to upgrade the index, etc.). No harm there I
think.
> 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
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
