On Thu, May 21, 2015 at 8:53 AM, Yonik Seeley <ysee...@gmail.com> wrote: > On Thu, May 21, 2015 at 12:55 AM, Robert Muir <rcm...@gmail.com> wrote: >> Honestly yonik: this is an API bug. If you have a public method, that >> refers to a package-private class, nobody can really use that public >> method you exposed. > > It's temporary - package private stuff will migrate to public. It's > not in it's final form and not meant to be a public API, but some > things have to be public for internal cross-package use. > > My point is that javadoc shouldn't fail stuff that java is happy with. >
But it is broken. The checker just tells you reality. If users click that package-private parameter link in the javadocs, they will get a 404 not found. And they wont be able to use the public method, because even though its public, it has a package-private class as parameter. The build did completely the right thing to fail here. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
