[
https://issues.apache.org/jira/browse/LUCENE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475132
]
Hoss Man commented on LUCENE-811:
---------------------------------
since SegmentInfos is final, and all of it's methods are (at best) package
protected i don't think it's a big risk to make it private again (without
requiring a bump to lucene-3.0.0)
I'm not sure if re-privatizing this class really neccessitates a 2.1.1 release
... it doesn't cause any bugs, and it does't really give people very much rope
to hang themselves with unless they are going out of their way to put stuff in
the org.apache.lucene.index package.
> Public API inconsistency
> ------------------------
>
> Key: LUCENE-811
> URL: https://issues.apache.org/jira/browse/LUCENE-811
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 2.1
> Environment: 2.1.0 release
> Reporter: Andrzej Bialecki
> Assigned To: Michael McCandless
> Priority: Minor
>
> org.apache.lucene.index.SegmentInfos is public, and contains public methods
> (which is good for expert-level index manipulation tools such as Luke).
> However, SegmentInfo class has package visibility. This leads to a strange
> result that it's possible to read SegmentInfos, but it's not possible to
> access its details (SegmentInfos.info(int)) from a user application.
> The solution is to make SegmentInfo class public.
--
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]
