If you want your generated documentation to contain links to classes such as java.lang.String , you must tell javadoc where to set the link. For example. on the command line you can say
-link http://docs.oracle.com/javase/7/docs/api/
This is not done automatically, as you need to decide which version to link to or whether you want to link to a local mirror. The command line may have several -link to link to several bibliographic documents.
Additional headers for each method are not supported by the standard doclet. But you can add your own tags below the text of the documentation. For example, you can define your own tag, for example @API.level.1 , and add it to the documentation comments below the text (in one line) and run javadoc with
-tag "API.level.1:a:Added in <a href='http://mycompany/Version1'>API Level 1</a>"
to create a line similar to your example (although it will be below the text).
No text formatting without HTML except {@code β¦} and {@literal β¦} . If you need more options, you need to write Taglets for a specific option. This is the easiest way to achieve a separation between the source code and the HTML code, which you think makes sense. This way you can define semantic @tags and implement specific formatting with Taglet.
Or you write the whole Doclet to have full control over the output, but I donβt think you want it.
But first you should start reading the JavaDoc documentation (again), as there may be some parameters that you have missed yet, which may not give the exact results that you asked for, but let me improve your documentation, which may change your priorities. (This can help to find out everything that is possible before you start coding things that are not yet possible.)
Holger
source share