[ https://issues.apache.org/jira/browse/LUCENE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475121
]
Michael McCandless commented on LUCENE-811:
-------------------------------------------
Indeed I did this as part of LUCENE-701, but I can't remember what on
earth my reasoning was.
I agree it's not necessary and we should make it package protected
again. I can make this fix.
Could we release a 2.0.1 that would include this (and anything else if
we need to)? I would volunteer to do the release mechanics since I
caused this (sorry) :(
I will also review what else I made public, and, be more careful in
the future to not relax protection unless it's absolutely needed.
> 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
> 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org