RFR: 8338981: Access to private classes should be permitted inside the permits clause of the enclosing top-level class [v7]

[Vicente Romero]

On Mon, 7 Oct 2024 15:30:38 GMT, Joe Darcy <darcy at openjdk.org> wrote:

> > > > > If this fix is proposing to align javac behavior with the JLS, while no spec change would be needed. A CSR would need to be filed for the behavioral change.
> > > > 
> > > > 
> > > > Hello! I am not familiar with CSR process. I tried to find a way to file it using java bug database, but could not find anything. Could you tell me what should I do and where, please?
> > > 
> > > 
> > > The CSR process is documented at https://wiki.openjdk.org/display/csr/Main. To create a CSR from a JBS issue, go to "More -> Create CSR."
> > > Myself and the other reviewers can help guide you in the process.
> > 
> > 
> > I`m sorry, but I can not find any "More" button on bug page. Do I need an account in JBS in order to file CSR (i assume do since on page load there is a blinking second button new "Open" one that asks me to log in)? I am not an Oracle employee so I don't have one, and I am also not the one to report this issue
> 
> Yes; someone with a JBS account will need to create the CSR.

I have just created a blank one: https://bugs.openjdk.org/browse/JDK-8341669

-------------

PR Comment: https://git.openjdk.org/jdk/pull/20718#issuecomment-2397542956