Skip to content

Commit 25a0be9

Browse files
arghya88nebhale
authored andcommitted
Remove Incorrect Documentation
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]
1 parent 7ddca83 commit 25a0be9

1 file changed

Lines changed: 0 additions & 2 deletions

File tree

docs/framework-java_opts.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,6 @@ The framework can be configured by creating or modifying the [`config/java_opts.
2424
| `from_environment` | Whether to append the value of the `JAVA_OPTS` environment variable to the collection of Java options
2525
| `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.
2626

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-
2927
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.
3028

3129
## Escaping strings

0 commit comments

Comments
 (0)