lucene-dev mailing list archives

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


Robert Muir commented on LUCENE-3930:

Sure, but this introduces additional complexity in setting up shell aliases or simply remembering
about it. This just feels wrong somehow (making life harder instead of simpler). I may take
a look at it at some point but I also remember having difficulties with multiple antlib definitions
in our stuff and I believe you it's a pain.

Right but honestly, while it might not be ideal, I don't think its a blocker? Having jars
in our source release is. Having the build OOM is. So I made a tradeoff.

If you (or any one else) has the time to look at stuff like this, it would be really appreciated:
thats why i created a branch:

We likely also won't have any of the IDE configurations working unless someone has the time
to jump into that, and I have no idea if the maven build will break by us not having jars
in the source tree. These are all things I will ignore without hesitation because they don't
need to block a release. If anyone wants to fix this stuff, just start committing to the branch,
i need your help... its just that simple :)

> 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