[
https://issues.apache.org/jira/browse/LUCENE-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253582#comment-13253582
]
Steven Rowe commented on LUCENE-3965:
-------------------------------------
A good first step would be to bring all Lucene contribs down to the same level
as {{core/}} and {{test-framework/}}; make a new {{module-build.xml}} that's
basically a copy of {{contrib-build.xml}}, and then make all the "internal"
modules switch to {{module-build.xml}}.
Moving {{modules/*}} and getting rid of {{contrib-build.xml}} could come later.
> consolidate all api modules in one place and un!@$# packaging for 4.0
> ---------------------------------------------------------------------
>
> Key: LUCENE-3965
> URL: https://issues.apache.org/jira/browse/LUCENE-3965
> Project: Lucene - Java
> Issue Type: Task
> Components: general/build
> Affects Versions: 4.0
> Reporter: Robert Muir
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
