This is quite a visible bug. Changed from priority 5 to 4.
This bug occurs only with -package option, so it's a lower-priority 4 bug.
The correct way to handle initializers would be for them to have unique
initializer access, e.g. in ClassDoc:
This will need to wait for the next major release. In the mean time,
the effect on output is minor and only occurs when using the "-package"
flag -- a rare thing.
It turns out this bug was introduced in the standard doclet while trying to
work around another bug in the javadoc tool. The underlying bug is that
to be a method. It isn't a method and shouldn't result in a method entry
in the javadoc API.