lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Miller <markrmil...@gmail.com>
Subject Re: [jira] Created: (LUCENE-1862) duplicate package.html files in queryParser and analsysis.cn packages
Date Thu, 27 Aug 2009 15:30:11 GMT
Chris Hostetter wrote:
> : > 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-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>   
I still have the same thought though - why not? Unless it takes a lot
longer to parse, why hide bad JavaDoc? We may maintain public JavaDoc
for users, but we maintain private JavaDoc for developers as well.

-- 
- Mark

http://www.lucidimagination.com




---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message