[
https://issues.apache.org/jira/browse/LUCENE-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248696#comment-13248696
]
Robert Muir commented on LUCENE-3965:
-------------------------------------
another idea: instead of having analysis/ with "submodules" underneath it,
we could flatten that too (like solr-dataimporthandler and
dataimporthandler-extras)
so we would have analysis-common, analysis-kuromoji, analysis-phonetic, etc.
Not sure if this really makes things simpler, but its flat. We don't have to do
it,
but maybe it could simplify the build and such to have this easy flat structure.
> Move lucene/core to modules/core, same with test-framework, etc
> ---------------------------------------------------------------
>
> 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]
