: > i'm thinking we should change the nightly build to set : > -Djavadoc.access=private so we at least expose more errors earlier. : > (assuming we also setup the hudson to report stats on javadoc : > warnings ... i've seen it in other instances but don't know if it requires : > a special plugin)
: If it gives more errors, shouldnt it be set always and everywhere? Why : not ... it doesn't just change the level of error checking -- it changes which methods get generated docs "access" refers to the java access level (public, protected, package, private) that should be exposed ... for releases we only want "protected" (the default in our build file) so we only advertise classes/methods/fields we expect consummers to use/override -- but as a side effect the javadoc tool never checks the docs on package/private members for correctness. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
