title: Most simple javadoc documentation for a derived exception regarding checkstyle SUN convention?
body: <p>I create a lot of exception classes, extending "Exception" and creating all constructors matching the constructors of the superclass "Exception". Eclipse generates this:</p>
  
  <pre><code>/**
   * 
   */
  package pone.interfaces;
  
  
  /**
   * @author wnck
   *
   */
  public class FancyException extends Exception {
  
  /**
   * 
   */
  public FancyException() {
      // TODO Auto-generated constructor stub
  }
  
  /**
   * @param message
   */
  public FancyException(String message) {
      super(message);
      // TODO Auto-generated constructor stub
  }
  
  /**
   * @param cause
   */
  public FancyException(Throwable cause) {
      super(cause);
      // TODO Auto-generated constructor stub
  }
  
  /**
   * @param message
   * @param cause
   */
  public FancyException(String message, Throwable cause) {
      super(message, cause);
      // TODO Auto-generated constructor stub
  }
  
  /**
   * @param message
   * @param cause
   * @param enableSuppression
   * @param writableStackTrace
   */
  public FancyException(String message, Throwable cause,
          boolean enableSuppression, boolean writableStackTrace) {
      super(message, cause, enableSuppression, writableStackTrace);
      // TODO Auto-generated constructor stub
  }
  }
  </code></pre>
  
  <p>I don't want to document all param tags because the constructors just match semantically the constructors of the base class.</p>
  
  <p>How can this fact be documented in a fast, clean and simple way using javadoc AND matching the SUN checkstyle rules?</p>
  
  <p>Regards wnck</p>