lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3930) nuke jars from source tree and use ivy
Date Thu, 29 Mar 2012 23:07:26 GMT


Chris Male commented on LUCENE-3930:

For solr/contrib/extraction, could not tika-parsers use transitive="true" to avoid specifying
versions for all parsers?

Having been the one to go through and add all those parsers and versions, there were many
times I wished I did use transitive.  But Robert is right, at this stage we get to see clearly
which jars we're using.  In the future I can perhaps see places in Solr for using transitive,
but in Lucene I think we should just be clear what dependencies we have.

Why do we let ivy download sources and javadoc jars? They can be excluded in ivy.xml

I quite like this because then we have the sources and javadocs when developing.  They're
downloaded once per dependency, no biggie?
> nuke jars from source tree and use ivy
> --------------------------------------
>                 Key: LUCENE-3930
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: general/build
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>            Priority: Blocker
>             Fix For: 3.6
>         Attachments: LUCENE-3930-solr-example.patch, LUCENE-3930-solr-example.patch,
LUCENE-3930.patch, LUCENE-3930.patch, LUCENE-3930.patch, LUCENE-3930__ivy_bootstrap_target.patch,
ant_-verbose_clean_test.out.txt, noggit-commons-csv.patch, patch-jetty-build.patch
> As mentioned on the ML thread: "switch jars to ivy mechanism?".

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message