[
https://issues.apache.org/jira/browse/LUCENE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987557#action_12987557
]
Robert Muir commented on LUCENE-2883:
-------------------------------------
bq. but with the distinction that changes in modules need to account for Solr
as well as Lucene.
I thought this was understood about modules anyway, that we move the code
there, all committers
have access and its shared code to support both projects.
hopefully we didnt screw this up in anyway for modules/analysis, I don't think
Solr lost anything here.
Separately, for the record, we didnt merge ALL of Solr's analysis stuff into
modules/analysis.
Some of this stuff really is solr-specific (e.g. ReverseWildCard support that
needs some schema + qp integration).
This really solr-specific stuff that isn't generally useful stayed in Solr.
So I think we should always consider this for future modules, it doesn't have
to be a binary decision,
but instead what is general and makes sense.
> Consolidate Solr & Lucene FunctionQuery into modules
> -----------------------------------------------------
>
> Key: LUCENE-2883
> URL: https://issues.apache.org/jira/browse/LUCENE-2883
> Project: Lucene - Java
> Issue Type: Task
> Components: Search
> Affects Versions: 4.0
> Reporter: Simon Willnauer
> Fix For: 4.0
>
>
> Spin-off from the [dev list |
> http://www.mail-archive.com/[email protected]/msg13261.html]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
