Javadoc is the standard output for Java APIs, and it’s really easy to build a Javadoc. The Javadoc is generated through something called a “doclet.” Different doclets can parse the Java annotations in different ways and produce different outputs. But by and large, almost every Java documentation uses Javadoc. It’s standard and familiar to Java developers.
Here are some other characteristics of Javadoc:
Select your project and package. Then in the right pane, select the classes you want included in the Javadoc. Don’t select the class that contains your main method.
Select which visibility option you want: Private, Package, Protected, or Public. Generally you select Public.
Your API probably has a lot of helper or utility classes used on the backend, but only a select number of classes will actually be used by your developer audience. These classes are made public. It’s the public classes that your developer audience will use that form the API aspect of the class library.
Here you can select if you want to omit some tags, such as @author and @deprecated. Generally you don’t include the @author tag, since it may only be important internally, not externally. You can also select different options in the Javadoc frame. If you have a custom stylesheet, you can select it here. Most likely you would only make superficial style changes such as with colors.
Here you can select an HTML page that you want to be your overview page in the Javadoc. You can select any HTML page and it will be included in the index.
Javadoc also checks your tags against the actual code. If you have parameters, exceptions, or returns that don’t match up with the parameters, exceptions, or returns in your actual code, then Javadoc will show some warnings.
Try removing a parameter from a method and generate the Javadoc again. Make sure the console window is open.
Get new posts delivered straight to your inbox.
© 2017, Tom Johnson