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-3965) consolidate all api modules in one place and un!@$# packaging for 4.0
Date Tue, 17 Apr 2012 13:07:17 GMT


Robert Muir commented on LUCENE-3965:

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.

Yeah I can rename these (at least temporarily) to something more appropriate after committing.

separately another TODO: its slightly confusing that core and friends aren't just another
and its confusing common-build.xml with its "module tasks" is included by lucene/build.xml,
its no module at all. 
(try ant -projecthelp from lucene/ and experiment with some of the common.XXXX tasks that
show up here).

But, this is the way trunk is today :) The tradeoff of this approach is that we keep all the
same logic
and its really not a drastic change...

I resisted doing these kind of cleanups because they have a chance of breaking something and
i think should
be cleaned up separately... but we should still look at it afterwards.

> 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