What about including ant.jar and then making a build file that can do all the magic we need for downloading and arranging things?
No matter the problem, Ant is the Swiss Army knife solution :) > On Feb 19, 2015, at 04:17, Jan Høydahl (JIRA) <[email protected]> wrote: > > > [ > https://issues.apache.org/jira/browse/LUCENE-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327147#comment-14327147 > ] > > Jan Høydahl commented on LUCENE-6259: > ------------------------------------- > > What about "java -jar get.jar deps.txt" > That would be 20 lines of code :) > The same program could download javadocs too.. > >> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
