On 23 November 2015 at 15:41, Chris Hostetter <[email protected]> wrote: > Does anybody understand the javadoc link generation enough to > understand why it isn't always trying to create links for these package > private classes? is there a way we can force it to always > create links so we can find API bugs like this with the link checker? (or > an alternative static analysis tool we can use to find these bad API > visibility bugs)
Well, Javadoc is open source these days (since version 8)...... No real contribution beyond that, I am afraid. I forked Javadoc for my solr-start.com purposes, but I did not look at the link generation: https://github.com/arafalov/Javadoc-IFramed/tree/master/src/main/java/com/outerthoughts/javadoc/iframed I suspect one of several Java static analysis tools probably detects public -> package private scenario. Is there a reason we are not using any of them (apart from "first run is too noisy"). Regards, Alex. ---- Newsletter and resources for Solr beginners and intermediates: http://www.solr-start.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
