crlib API allows engines to omit some configuration options from their configuration docs if they are expected to be set directly by JVM instead of the user. This is not correct because it makes engine document not only the behavior of itself but also of JVM which they don't have control over.
Instead we should let engines document all their options and make it JVMs responsibility to somehow tell the user what options are controlled by the JVM.
Instead we should let engines document all their options and make it JVMs responsibility to somehow tell the user what options are controlled by the JVM.
- relates to
-
JDK-8350845 [CRaC] Support C/R engines in form of a library
-
- Resolved
-
- links to
-
Commit(crac) openjdk/crac/410d0e16
-
Review(crac) openjdk/crac/220