-
Bug
-
Resolution: Fixed
-
P3
-
1.3.0
-
beta3
-
sparc
-
solaris_2.6
This is a cosmetic bug about how the parts of the declaration lines up on
the generated page.
Without -linksource option, the exception in the throws clause
lines up vertically with the types of the arguments above it:
public java.lang.String methodWithAllTags(java.lang.String s1,
java.lang.String s2)
throws java.lang.ClassNotFoundException
Notice the "j" in java.lang.ClassNotFoundException is directly
below the "j" in java.lang.String.
However, when -noqualifier is used (such as "-noqualifier all"),
they no longer line up:
public String methodWithAllTags(String s1,
String s2)
throws ClassNotFoundException
The amount of leading space ahead of the throws clause should be adjusted
to account for the fact that the qualifiers are missing. It should look
like:
public String methodWithAllTags(String s1,
String s2)
throws ClassNotFoundException
This example is taken from sample-src/com/package1/Class1.java, which
is attached to this bug.
the generated page.
Without -linksource option, the exception in the throws clause
lines up vertically with the types of the arguments above it:
public java.lang.String methodWithAllTags(java.lang.String s1,
java.lang.String s2)
throws java.lang.ClassNotFoundException
Notice the "j" in java.lang.ClassNotFoundException is directly
below the "j" in java.lang.String.
However, when -noqualifier is used (such as "-noqualifier all"),
they no longer line up:
public String methodWithAllTags(String s1,
String s2)
throws ClassNotFoundException
The amount of leading space ahead of the throws clause should be adjusted
to account for the fact that the qualifiers are missing. It should look
like:
public String methodWithAllTags(String s1,
String s2)
throws ClassNotFoundException
This example is taken from sample-src/com/package1/Class1.java, which
is attached to this bug.