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 Wed, 28 Mar 2012 00:13:22 GMT


Chris Male commented on LUCENE-3930:

Great stuff Robert.  I've come into the discussion a little late but I'll help where I can.

bogusly every contrib/module currently needs an ivy.xml (even with no dependencies). I'd like
to remove this but i just havent mucked with it yet.

I don't think this is so bad? It shows that the contrib/module is properly configured and
that the ivy integration was 'done' when the module was created.  I think it might also help
IDEs if every module is consistent.
> 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
>         Attachments: LUCENE-3930.patch, LUCENE-3930.patch, LUCENE-3930.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