On Wed, 3 Mar 2021 13:21:06 GMT, Kevin Rushforth <[email protected]> wrote:
>> A couple other comments: >> >> 1. Previous release notes were sorted first by subcomponent and then by bug >> ID. You might consider whether to do that again for 16? >> 2. The following bug was called out during the CSR as needing a release note >> to highlight the new log warning: >> [JDK-8256362](https://bugs.openjdk.java.net/browse/JDK-8256362): JavaFX must >> warn when the javafx.* modules are loaded from the classpath >> I think I'm on the hook for that one, so I can provide you the proposed text >> later today, in case you want to include it. > > For the last couple releases, I generated the list of bugs to add to release > notes, and yes, I typically exclude backports for that reason (it isn't > perfect, but it also excludes the issues labeled with the `hgupdate-sync` > label, which can be added to indicate an issue synced in from a prior > release). > > Here is the same filter I used in the past, updated for JavaFX 16 for > comparison: > > https://bugs.openjdk.java.net/issues/?filter=40381 > > You'll notice that it excludes test bugs and build issue (so the "GitHub > Actions" bugs don't show up, for example) Below is the release note for the warning, taken from [this release note sub-task](https://bugs.openjdk.java.net/browse/JDK-8262948): --- ### JavaFX runtime logs a warning if javafx.* modules are loaded from the classpath The JavaFX classes must be loaded from a set of named `javafx.*` modules on the _module path_. Loading the JavaFX classes from the classpath is not supported. The JavaFX runtime logs a warning at startup if the JavaFX classes are not loaded from the expected named module. See [JDK-8256362](https://bugs.openjdk.java.net/browse/JDK-8256362) for more information. ------------- PR: https://git.openjdk.java.net/jfx/pull/414
