On Wed, May 20, 2015 at 11:38 PM, Yonik Seeley <ysee...@gmail.com> wrote: > Seems like a bug in javadoc if it fails on valid java code with no > javadoc specified on the involved classes.
Why is it a bug in javadoc? It generates plenty of javadoc for your code even if you don't specify it, like method signatures, return types, arguments. And for these links are generated... The current javadocs level is 'protected' so that class isn't included, hence the broken link. 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. Try it. This is just the only way we currently have to detect API bugs like this. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
