-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[OPENJDK-78] Re-work JAVA_OPTS to override script-calculated java options #302
Conversation
I was thinking we needed to either continue to support |
245b31d
to
1f9415e
Compare
The PR now better reflects how I remember |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should have a test which verifies that if JAVA_OPS
and JAVA_OPTS_APPEND
are both specified, then only JAVA_OPTS
are being added. I.e. JAVA_OPTS_APPEND
is an override for the default options. JAVA_OPTS
are a replacement.
Good idea: I've just pushed one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please clarify the description of JAVA_OPTS_APPEND
.
example: "-verbose:class" | ||
- name: JAVA_OPTS_APPEND | ||
description: User specified Java options to be appended to generated options in JAVA_OPTS. | ||
description: User specified Java options to be appended to the generated options. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add that this variable has no effect if JAVA_OPTS
is set in the description.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't mind doing so, and I will. I originally decided not to because I wasn't also going to annotate all the other variables that are disabled by specifying JAVA_OPTS
, but, due to their similar name and behaviour I can see that this one should be treated differently.
This is a very old and (I think) almost unused option to provide additional JVM options via a file inside the container. Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
If JAVA_OPTS is defined, don't attempt to expand the various options we might otherwise provide: debug options, proxy settings, JVM/GC tuning, etc. https://issues.redhat.com/browse/OPENJDK-78 Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Signed-off-by: Jonathan Dowland <jdowland@redhat.com>
Again, the failing test here passes locally and I think is sporadic on GH actions. |
https://issues.redhat.com/browse/OPENJDK-78
This is a first attempt at a way of short-circuiting all Java options
generation.