You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously the JAVA_OPTS documentation mentioned an exclusion of any memory
configuration flags. This exclusion was dropped in v4.0 and was never
removed. This change removes that out of date documentation.
[resolves#592]
Copy file name to clipboardExpand all lines: docs/framework-java_opts.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,8 +24,6 @@ The framework can be configured by creating or modifying the [`config/java_opts.
24
24
| `from_environment` | Whether to append the value of the `JAVA_OPTS` environment variable to the collection of Java options
25
25
| `java_opts` | The Java options to use when running the application. All values are used without modification when invoking the JVM. The options are specified as a single YAML scalar in plain style or enclosed in single or double quotes.
26
26
27
-
Any `JAVA_OPTS` from either the config file or environment variables that configure memory options will cause deployment to fail as they're not allowed. Memory options are configured by the buildpack and may not be modified.
28
-
29
27
Any `JAVA_OPTS` from either the config file or environment variables will be specified in the start command after any Java Opts added by other frameworks.
0 commit comments