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:31:18 GMT


Robert Muir commented on LUCENE-3965:

running a final test first. I committed the fixes to nightly/

However, we could encounter a failed build from the svn check, due to the removal
of the bogus build directories and their svn:ignores (would just be leftover relics).

Once i commit I will ask Uwe to clean the workspaces to (hopefully) prevent that,
but its possible one build could slip through... (and of course the possibility
i have some other bugs)
> 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