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 02:47:26 GMT


Chris Male commented on LUCENE-3930:

bq. Now we have the problematic patched jars and the renamed unreleased jars.

For the unreleased jars, can we just include their source in our source? This would work for
commons-csv and noggit which are the only two in solr/lib.  They're both very small jars with
only a handful of java files.

I'm running into bigger problems with the libs in the solr contrib langid.  The langdect jar
is from a revision I cannot find in its googlecode project (due to a switch from svn to git)
and the jsonic jar it depends on isn't available in ivy accessible repos, only version 1.2.8
> 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, ant_-verbose_clean_test.out.txt
> 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