[ 
https://issues.apache.org/jira/browse/LUCENE-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903983#action_12903983
 ] 

Simon Willnauer commented on LUCENE-2628:
-----------------------------------------

bq. I'm not sure I like this. Most of the stuff in the util package should be 
marked lucene.internal anyway, so such a jar would be of minimal use.
You are probably right here and I did really expect that to be a serious 
option. I was just curious if other would like that so we could discuss the 
pros and cons. I personally think if it is only one class people should 
duplicate that code and try to keep in sync on their own. Yet the whole code 
duplication discussion is a valid point but not worth the hassle here. 

bq. Although some might consider utility stuff like this useful, I don't think 
we should be creating artifacts that arent focused on search. 
we should keep this stuff internal.
I actually don't agree on that, if a nice stand alone jar comes out of what we 
do here we should not hesitate to make it usable without the core but that 
might be a super rare case and might even have never happened before here but 
generally being against such a thing doesn't seem to be community or cross 
project friendly to me. I can understand the reasons why this issue has been 
created and I support not to push stuff towards a third party dependency from a 
lucene point of view (that is just not an option and should stay like that) but 
still we can try working with others to use lucene code in a more convenient 
way, search related or not.

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to