JDK-8334726 : Remove accidentally exposed individual methods from Class-File API
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang.classfile
  • Affected Version: 23
  • Priority: P4
  • Status: In Progress
  • Resolution: Unresolved
  • Submitted: 2024-06-21
  • Updated: 2024-07-01
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 24
24Unresolved
Related Reports
CSR :  
Description
A few methods are exposed by Class-File API by accident: they see no use by any client, and their continued exposure will only be a maintenance in the long run. They are:
 - ModuleAttributeBuilder.build: this builder is already using the build(Consumer<Builder>) model, so the build method is useless.
 - CodeRelaber.relabel: internal access method, can just be hidden
 - ConstantPoolBuilder.writeBootstrapMethods: users shouldn't access the writing functionalities

These methods can be easily removed and should be removed.
Comments
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/19832 Date: 2024-06-21 14:38:44 +0000
21-06-2024