Chris Hostetter wrote: > : > you obviously haven't tried "ant javadocs -Djavadoc.access=private" > lately > : > ... i'm working on cleaning that up at the moment. > > : tried it? I'm not even aware of it. Not mentioned in the release todo. > > yeah ... it's admittedly esoteric, but it helps surface bugs in docs on > private level methods (which are useful for long term maintence) > > 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) > > > -Hoss > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > If it gives more errors, shouldnt it be set always and everywhere? Why not ...
-- - Mark http://www.lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
