JDK-8074282 : Finder framework should suggest places for using private interface methods in lieu of private nested classes
  • Type: Enhancement
  • Component: tools
  • Sub-Component: javac
  • Affected Version: 9
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2015-03-03
  • Updated: 2017-10-17
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.
Other
tbd_minorUnresolved
Related Reports
Relates :  
JDK-8071453 - Allow interface methods to be private
Description
With the release of https://bugs.openjdk.java.net/browse/JDK-8071453, JDK's own code
base could begin taking advantage of the new capability to use private methods in interfaces.
In the absence of such capability till date, programmers have had to resort to awkward and
clumsy workarounds such as having to create a private nested class to park such methods.

This ticket is to request an enhancement to the finder framework in javac to issue diagnostics
indicating places where such private nested class usage could be replaced with the more direct
private interface methods approach.
Comments
I am looking for concrete examples of anecdotal "awkward and clumsy workarounds". Once these become available, the timeline can be evaluated
17-05-2016