bmarwell commented on issue #10747: URL: https://github.com/apache/maven/issues/10747#issuecomment-3472615554
> It avoids the need to bundle native code together with the Java code (provided that the API that we invoke is in C, not C++ or other language), but we would still have the warning at Java launch time and the need to add the `--enable-native-access` option. Yes, true. My intention was to at some point either: 1. not ship jansi anymore and use system libraries, so this message does not pop up 2. load jansi lazily (e.g. if not disabled by an ENV var), which is a bit easier to do with FFM. So yes, you are right, it does not solve the issue, but other strategies will appear. > I think maven should not do this operation on its own It really should not and may trigger warnings in intrusion detection systems, so reminding the user is the way to go, I agree. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
