The values of static final fields must be specified in the API specification.
Until now we have relied on developers writing in the values by hand in the
body of the doc comments, which very few do.
More technically, we would publish the value for: (according to Josh)
All primitive and String final static fields that are
initialized to compile-time constant expressions.
To ensure that this be done accurately, Javadoc should automate this,
inserting the value in the generated output.
This needs to be done for both the standard and MIF doclets.
Note that the implementation should be sure to specify the values for
private and package-private static final fields in those cases when the
user supplies the -private or -package flags to javadoc.
Once this is done, we should create a doc bug report to remove the
manually-added values from the comment bodies.
If the value is added to the signature, it may be necessary to modify the
localization pre-process doclet to strip off the value, because the
signature is used as a key in the comment (.cmnt) file to uniquely
identify the comment.