[External] : Re: How to open a package from a module in the boot layer to a module in another layer?

[Code Ranger]

On 1/14/25 18:50, Alan Bateman wrote:
>
> For the JDK modules then I think we need to understand more about the issues you are dealing with. Is this about serialization, or is this plugin code that needs to be fixed to not depend on JDK internals. We get it that you can't know all the bad things that these plugins might do but this doesn't mean it's a problem that should be solved. 

Why did you add --add-* parameters to JDK? Is it a problem that should be solved?

We are going in circles. I have explained in great detail the limitations of the --add-* parameters. I provided a visual representation of the issue. I keep emphasizing over and over again — the issue is not whether to add custom directives or not, but rather to add them DYNAMICALLY. I also thoroughly explained the limitations of module.addX() and why they can't solve the problem.

Regarding the agent — who is ready to add such an agent to their application to manage module directives and present it to the community?

I have nothing else to add. Really, nothing. The ball is in your court. Either reopen the issue, or Java developers, to the delight of developers in C#, Python, JS, etc., will have to write such instructions for their plugins:

1. Install the plugin.
2. Stop the application.
3. Add --add-exports ..., --add-opens ....
4. Restart the application.

Best regards, CR