lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-811) Public API inconsistency
Date Fri, 23 Feb 2007 10:52:06 GMT


Michael McCandless commented on LUCENE-811:

> I think making some methods public is fine, so long as the class is
> kept package-private.

But, for a package-private final class, marking un-inherited
methods/fields public doesn't enable any additional access since the
class itself is only visible within the package (I think)?  Or am I
missing something basic about Java's access protections?

> Public API inconsistency
> ------------------------
>                 Key: LUCENE-811
>                 URL:
>             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
>         Attachments: LUCENE-811.patch
> 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 ( 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:
For additional commands, e-mail:

View raw message