Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
maybe even better: implement a solution as we have it with the Domino server's "java.policy" file:
there we can build our separate "java.pol" file holding all custom policy settings. that ensures that any updates can renew the existing "java.policy" and still keep any custom settings.
In case of "jvm.properties" we could use something like a separate "jvm_custom.properties" (or whatever you want to name it) which never gets touched by an update, and whose contents are still able to override conflicting settings from the standard file