Vaadin Flow 24.4.7
Changes since 24.4.6
Fixes
-
Prevent NPE when creating init parameters (#19856)
Commit · Pull request · IssueServletConfig might contain init parameter with null values. This is however not supported by java Properties class. This change adds a null check and logs offending keys for debugging purpose.
-
Use 8080 as the default launch port for opening the browser (#19833)
Commit · Pull request · Issue -
Use Thread context ClassLoader for loading I18n ResourceBundle (#19791)
Commit · Pull request · IssueResourceBundle caches resources internally, this affects translation resources for the I18n feature. However, after a hot reload of a SpringBoot application in dev mode, up-to-date translations are expected in the output. With this change, a RestartClassLoader is used in SpringBoot applications for loading translation ResourceBundle, so that the translation bundles are reloaded on hot reload.
-
Use URLClassLoader with ResourceProvider in Maven plugins (#19781)
Commit · Pull request · IssueResourceProvider ignored the actual project's resources when using the default ClassLoader. This resulted in loading
vaadin-featureflags.properties
from the vaadin-dev-bundle jar, even though there is a file in the project.