[
https://issues.apache.org/jira/browse/LUCENE-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904142#action_12904142
]
Simon Willnauer commented on LUCENE-2628:
-----------------------------------------
I agree with Robert and Shai on this issues and that other folks should just
pull out the class they need. Adding it to commons makes sense and they should
likely go that way. Still we should try to move the modularization forward as
we did with analyzers etc.
Yet making a module out of almost 100% lucene.internal API doesn't make sense
and would bring lots of disadvantages as folk have outlined above.
bq. But I'll fight this fight in another issue when I propose such a module
Once it is beneficial for Lucene I am with you! I was only one more option
which came to my mind.
That said, I suggest to close this issue and move forward. If nobody objects I
am going to do that by the end of the day.
> Extract OpenBitSet to Apache Commons
> ------------------------------------
>
> Key: LUCENE-2628
> URL: https://issues.apache.org/jira/browse/LUCENE-2628
> Project: Lucene - Java
> Issue Type: Wish
> Reporter: Stu Hood
>
> o.a.l.util.OpenBitSet is a great alternative to java.util.BitSet, and it is
> generally useful outside of the search field. It would be great if OpenBitSet
> were available outside of Lucene proper, perhaps as part of Apache Commons.
> Aside from the communication required to accomplish this, there is the small
> issue of OpenBitSet extending o.a.l.search.DocIdSet in Lucene 3.0. There is
> very little logic contained in DocIdSet, so it could probably become an
> interface: Lucene proper could then extend the extract version of OpenBitSet
> to implement DocIdSet.
--
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]