#2 WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning

[Anonymous]

Thanks for keeping ARECA alive!
I have areca-backup-8.2.4 running on my PC, but in the CL dialog it includes this warning:

WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled

I'm not sure whether there's anything I can change in my current Java install to address this - I'm ignoring it for now, but it sounds like future releases of Java may require a response to this. Do you have any advice?

Philip

[Bugtamer]

Hi Philip,

Yes, I think it's as you indicate, something to be prepared for in the near future.

From what I've been able to find out, it seems that a new parameter (e.g., java --enable-native-access=ALL-UNNAMED [...] or anything more specific than ALL-UNNAMED) will need to be added to the launchers (areca_run.bat and areca_run.sh), but I haven't been able to test it to confirm since I haven't been able to reproduce the message.

Could you tell me:

1. Operating system (I've tested both Windows and Linux) and, if you're using Linux, whether you have ACL support.
2. Java version, architecture, and vendor (I've tried OpenJDK 24 from Temurin x86_64)
3. Where or how to make the message appear? (I haven't seen it in areca_cl, logs, or in the GUI)

Could you tell me these three pieces of information?
Thanks