JDK-8039028 : [javadoc] refactor the usage of Util.java
  • Type: Bug
  • Component: tools
  • Sub-Component: javadoc(tool)
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2014-04-02
  • Updated: 2014-07-21
  • Resolved: 2014-07-12
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b23Fixed
Related Reports
Blocks :  
Duplicate :  
Description
com.sun.tools.doclets.internal.toolkit.util.Util class is comprised of static utility methods, this is very
inconvenient makes it hard to implement the Doc to Element conversion work see JDK-8035473
Comments
(separately) some of the methods on Util might have better places elsewhere.
02-04-2014

So presumably, we want to make methods non-static, thus requiring clients to have an instance of Util Once Util can have state, it could presumably contain a configuration, so the various methods that take a configuration as a parameter will no longer need to do so.
02-04-2014