How to stop Javadoc from using fully qualified name?

How to stop Javadoc from using fully qualified name?

I'm using the Javadoc tool to document some code, and the results uses fully qualified names for system classes, such as java.lang.String. Is there a way to stop that specifically for classes in the java.* and javax.* heirarchy?

I'm using the Javadoc tool to document some code, and the results uses fully qualified names for system classes, such as java.lang.String. Is there a way to stop that specifically for classes in the java.* and javax.* heirarchy?

For example, a method definition like this:

    * @param field String to write.
    * @throws IOException If the underlying stream throws an exception.
    */
   public void writeField( String field ) throws IOException {
      // etc.

Produces Javadoc output like this:

writeField

public void writeField​(java.lang.String field) throws java.io.IOException

...etc.

Parameters: field - String to write. Throws: java.io.IOException - If the underlying stream throws an exception.

I'd like the reference to java.lang.String to be just String, and the reference to java.io.IOException likewise to be just IOException.

Any ideas?

Angular 9 Tutorial: Learn to Build a CRUD Angular App Quickly

What's new in Bootstrap 5 and when Bootstrap 5 release date?

Brave, Chrome, Firefox, Opera or Edge: Which is Better and Faster?

How to Build Progressive Web Apps (PWA) using Angular 9

What is new features in Javascript ES2020 ECMAScript 2020

Java Fundamentals: Learn Java for absolute beginners |Simpliv

Java Fundamentals: Learn Java for absolute beginners

Java Essentials : Learn Core Java From Basic to Advance

Learn Java Programming Using Practical Assignments. Start Building Back-end Web Applications Robust Test Automation Frameworks By End Of The Course. Learn More!

Fundamentos de Java: Aprende Java desde cero, sin misterios | Simpliv

Fundamentos de Java: Aprende Java desde cero, sin misterios