Vaadin Framework 8.21.0

Starting with Vaadin 8.21.0, Vaadin Framework 8 releases will be made available through a private Maven repository. To gain access to this private repository, you can find instructions here. Vaadin Framework 8 releases will eventually be exclusively available through this private repository, but for the time being artifacts will also be released to Maven Central.

Changes in Vaadin 8.21.0:

• Framework 8 builds are now made on Java 11. The resulting JARs are still fully compatible with Java 1.8 runtimes, but only Java 11 SDKs are supported for building Framework 8 for the 8.21 series.

  Build-time compatibility with Java 17 SDKs is being investigated, but is not yet available.

  If you wish to run Vaadin 8 on Java 9+ JREs, you must set the Java environment value java.locale.providers=COMPAT, otherwise locale dependent conversions (country code, currency, etc) WILL be inconsistent with Java 8 behavior, potentially leading to data loss.

  Minimum Maven version to build Vaadin 8 is now 3.6.2.

  Included new dependencies:

  • javassist version 3.29.2-GA
  • maven-enforcer-plugin 3.3.0

  Updated supporting Maven plugins:

  • maven-clean-plugin from 3.0.0 to 3.2.0
  • maven-compiler-plugin from 3.5.1 to 3.11.0
  • maven-site-plugin from 3.5 to 3.12.1
  • maven-jar-plugin from 2.6 to 3.2.2
  • maven-surefire-plugin from 2.19.1 to 2.22.2
  • maven-failsafe-plugin from 2.19.1 to 2.22.2
  • maven-dependency-plugin from 3.0.1 to 3.5.0
  • exec-maven-plugin from 1.6.0 to 3.1.0
  • versions-maven-plugin from 2.3 to 2.15.0
  • build-helper-maven-plugin 1.10 to 1.12
  • maven-source-plugin 3.0.1 to 3.2.1
  • maven-checkstyle-plugin from 3.2.0 to 3.2.2

• Upgraded GWT dependency to 2.9.0 in order to make Framework 8 more compatible with other Vaadin products and modern build environments, as well as to improve compatibility with modern browsers.

• Fixed all JavaDoc generation errors and cleaned up some API documentation along the way, resulting in better IDE compatibility and cleaner formatting of the resulting documentation.

• Fixed a bug in the long polling push transport when the sync id check is disabled, leading to the server continuously pushing.
  This is a backported fix from Flow, see issue #17237 and pull request #17238.

• Added new API in VaadinSession.java which allows setting priority of UIProviders. The function VaadinSession.addUIProvider now takes an extra integer parameter, which makes it possible to explicitly set priority of the UI providers as they're added.

  Additionally, the functions VaadinSession.getUIProviderPriority and VaadinSession.setUIProviderPriority were added, which can be used together with VaadinSession.getUIProviders to alter the ordering of all UI providers added to the Session.

  It is also possible to specify the priority of the default UI providers by setting the UIPriority value as part of the DeploymentConfiguration.

  This does not alter default behavior. The default UIProvider priority is 0; higher values get processed first. Providers with the same priority will be processed in the order they were added.

  See the VaadinSession JavaDoc for more information.

• Updated internal Jetty depdency from version 9.4.48.v20220622 to version 9.4.51.v20230217 to avoid a false positive security alert. The internal Jetty server is only used for running tests at build time.

• Updated plexus-archiver version in vaadin-maven-plugin to 4.8.0 in order to fix a potential security vulnerability.

Vaadin Framework 8.20.3

• Fixed an issue where compile-time license checking would fail on CI servers with release-only license files.
• Pinned nimbus-jose-jwt version in order to ensure that apps can still run under included Jetty on Java 8 VMs. Newer versions of nimbus-jose-jwt include a meta-info class that JVM 8 implementations cannot load. nimbus-jose-jwt was included as a transitive dependency.

Vaadin Framework 7.7.40

The Vaadin Framework 7.7.40 is an extended-support release with the following changes:

• Fixed an issue where compile-time license checking would fail on CI servers with release-only license files.

Vaadin Framework 7.7.39

The Vaadin Framework 7.7.39 is an extended-support release with the following changes:

• Added the Flatten Maven Plugin
• A fix to compute the correct path to a war file from the resource URL
• General pom.xml and project structure fixes

Vaadin Framework 8.20.2

This is a maintenance release. Changes from 8.20.1:

• Removed mentions of NetBeans Plugin, since it has not been maintained and is no longer usable in modern versions of NetBeans. Usage of NetBeans for Vaadin development is still possible, but it is not explicitly supported through a special plugin.
• Improved build system; maven-flatten-plugin is now correctly invoked and build system related version numbers were bumped. This change should not affect users.

Vaadin Framework 8.20.1

This is a maintenance release. Changes from 8.20.0:

• Fixed a bug in TwinColSelect, which caused incorrect layouting on Firefox on some platforms. The issue was similar to the problem discussed in #9175
• Updated license-checker to the latest available version for better user experience and MPR compatibility.
• Mitigated false positive reports of security vulnerabilities by adding maven-flatten-plugin to the build process. This strips out testing artifacts from the released POMs so that the released artifacts are not marked as vulnerable.

Vaadin Framework 7.7.38

The Vaadin Framework 7.7.38 is an extended-support release with the following changes:

• A fix to preserve push messages in cache until they are seen by client
• A fix to prevent concurrent disconnect and push operations
• A change to close push connection immediately after refresh.

Vaadin Framework 8.20.0

Changes in this version:

• Moved vaadin-portlet package contents from com.vaadin.server to com.vaadin.portlet namespace. This is a BREAKING CHANGE and will require you to update your imports. This is a necessary change in order to be able to support OSGi deployments (specifically under the latest Liferay 7 releases.

  • PLEASE NOTE THAT THIS IS A BREAKING CHANGE! - you need to update references to classes provided by vaadin-portlet from the com.vaadin.server to the com.vaadin.portlet namespace. The complete list of classes is as follows:

    • com.vaadin.portlet.LegacyVaadinPortlet
    • com.vaadin.portlet.RestrictedRenderResponse
    • com.vaadin.portlet.VaadinPortlet
    • com.vaadin.portlet.VaadinPortletRequest
    • com.vaadin.portlet.VAadinPortletService
    • com.vaadin.portlet.VaadinPortletSession
    • com.vaadin.portlet.WrappedPortletSession

    and

    • com.vaadin.portlet.communication.PortletBootstrapHandler
    • com.vaadin.portlet.communication.PortletDummyRequestHandler
    • com.vaadin.portlet.communication.PortletListenerNotifier
    • com.vaadin.portlet.communication.PortletStateAwareRequestHandler
    • com.vaadin.portlet.communication.PortletUIInitHandler

    If you've referenced any of these classes, they will have been in the com.vaadin.server and com.vaadin.server.communication packages, respectively.

• Improved OSGi packaging for vaadin-portlet. See issue #12575.
• Fixed an issue where push connections could get stuck when using @PreserveOnRefresh as requests intended for a new push connection would instead be queued on an old one. Now old connections are closed immediately on reconnect. See issue #12577.
• Fixed Push connection operations synchronization so that a connection won't be disconnected while there are messages pending. This would result in NullPointerExceptions being thrown. Makes the isConnected() call correctly reflect current state. This is a backported fix from Flow. See Flow issue #15571.
• Fixed an issue where undelivered push messages would get lost, resulting in a need for UI resynchronization. Push messages are now kept in cache until a client acknowledges receipt. This is a backported fix from Flow. See Flow issue #15205.
• Improved performance in UIs with assertions enabled. Some assertions would check for the presence of MPR on every run. MPR is now only detected once and the check result is cached. See issue #12572.

Vaadin Framework 8.19.0

• Changed license from Commercial Vaadin Developer License 4.0 to Vaadin Commercial License version 1. This change does not affect active subscribers, but it does mean that future releases of Vaadin Framework may move from dev- and build-time license checking to runtime license checking. Version 8.19.0 does not do that yet.
  See LICENSE file in the downloadable package or the Vaadin Commercial License and service terms document for more information.
• Fixed issue #12562. The internal state of ComboBox got confused when adding new items after calling clear().
• Improved the vaadin-server-mpr-jakarta and vaadin-compatibility-server-mpr-jakarta POM dependency definitions such that these packages do not pull in vaadin-server and vaadin-compatibility-server as unwanted dependencies, respectively.
• Fixed a number of assertion functions which would fail when MPR was in use. Improves testability of the framework and should allow running with assertions enabled in MPR configurations.
• Removed logging of Atmosphere version while MPR is in use. This fixes runtime failures under some configurations.
• Updated Atmosphere to version 2.4.30-vaadin5 in order to make Vaadin Framework 8 compatible with Jetty 10.
• Updated Vaadin License Checker to version 1.11.2 to support new license model.

Vaadin Framework 7.7.37

The Vaadin Framework 7.7.37 is an extended-support release with the following changes:

• license updated to VCL-1
• updated server-MPR artifact POM to remove dependency on server