lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3965) consolidate all api modules in one place and un!@$# packaging for 4.0
Date Tue, 17 Apr 2012 12:53:18 GMT


Steven Rowe commented on LUCENE-3965:

+1 to commit - good progress!

Tests work from the top level, and I tried {{ant test}} in a couple of modules' directories,
which also worked.  Build output all seems to be going to the right place (under {{lucene/build/}}).

I scanned the changed build files, and I didn't see any problems.

I searched {{\*build.xml}} for "modules/" and "contrib".  "modules/" seems to be gone, but
there are several names that still have "contrib" in them (e.g. {{test-contrib}}) in {{lucene/build.xml}}
and {{lucene/common-build.xml}}.  These names can be fixed later.

I didn't look at javadocs or packaging - I assume anything you've done there will be better
than it was :).
> consolidate all api modules in one place and un!@$# packaging for 4.0
> ---------------------------------------------------------------------
>                 Key: LUCENE-3965
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: general/build
>    Affects Versions: 4.0
>            Reporter: Robert Muir
>         Attachments: LUCENE-3965.patch, LUCENE-3965.patch, LUCENE-3965.patch, LUCENE-3965.patch,
LUCENE-3965_module_build.patch, LUCENE-3965_module_build_pname.patch
> I think users get confused about how svn/source is structured,
> when in fact we are just producing a modular build.
> I think it would be more clear if the lucene stuff was underneath
> modules/, thats where our modular API is.
> we could still package this up as lucene.tar.gz if we want, and even name
> modules/core lucene-core.jar, but i think this would be a lot better
> organized than the current:
> * lucene
> * lucene/contrib
> * modules
> confusion.

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