Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up Javadoc #13699

Closed
nik9000 opened this issue Sep 21, 2015 · 3 comments · Fixed by #13702
Closed

Clean up Javadoc #13699

nik9000 opened this issue Sep 21, 2015 · 3 comments · Fixed by #13702
Assignees
Labels
>docs General docs changes

Comments

@nik9000
Copy link
Member

nik9000 commented Sep 21, 2015

We're disabling doclint in #13689 so the javadocs that we have will compile. We should get the javadocs to the point where they pass doclint - or at least pass some checks. We're not really sure what standards we should have for Javadoc but right now we don't have any.

@nik9000 nik9000 added the >docs General docs changes label Sep 21, 2015
@rmuir
Copy link
Contributor

rmuir commented Sep 21, 2015

FWIW this is what lucene uses right now:

  <property name="javadoc.doclint.args" value="-Xdoclint:all -Xdoclint:-missing"/>
  <property name="javac.doclint.args" value="-Xdoclint:all/protected -Xdoclint:-missing"/>

Available options are: accessibility, html, missing, reference, or syntax

Maybe we should at least start with html, reference, syntax and fix the errors in docs we already have.

accessibility and missing require adding more (e.g. captions for images/tables, and javadocs for methods that don't currently have any).

And the other trick is to pass doclint options to javac too, meaning the compile will just fail (its a fast check) and you don't need to run any additional build target. See the example, for that to work, you have to specify the access level that you normally generate javadocs for (e.g. protected).

@nik9000
Copy link
Member Author

nik9000 commented Sep 21, 2015

Maybe we should at least start with html, reference, syntax and fix the errors in docs we already have.

And the other trick is to pass doclint options to javac too, meaning the compile will just fail (its a fast check) and you don't need to run any additional build target. See the example, for that to work, you have to specify the access level that you normally generate javadocs for (e.g. protected).

I think this is the right way to start on this. I suspect there are plenty of Javadoc errors to fix just with those options.

@rmuir rmuir self-assigned this Sep 21, 2015
@rmuir
Copy link
Contributor

rmuir commented Sep 22, 2015

I suspect there are plenty of Javadoc errors to fix just with those options.

That is the understatement of the year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>docs General docs changes
Projects
None yet
2 participants