Vaadin 19.0.5

Vaadin consists of a set of web components, a Java web framework, configurable themes, tools and a set of app templates.

This is a maintenance release of Vaadin.
See the full release notes for vaadin 19.0 in GitHub releases, including new features, getting started, supported browsers and other technologies, and migration notes.

Visit vaadin.com to get started.

New and Noteworthy

Here are the highlighted new and improved features in this maintenance release.

Vaadin Flow (6.0.6)

• Fixes:

  • ⧉ Compare file content from stream. PR:10640

    Compare jar file content and existing target file content before writing to disk.

  • ⧉ Do not override user pinned versions with pnpm. PR:10635. Ticket:9793

    Any user defined (package.json / NpmPackage-annotation) versions will not be overridden by based on the platform versions (versions.json file). This means that the users will have to remember to also remove their pins after those are not needed anymore or they will stay on using old versions, which is the same as with Maven overrides.

  • ⧉ Include redirectUrl in the return value of login(). PR:10663

    It includes the redirectUrl in the return value of the login() helper. So that if the user has defined a request cache or a defaultSuccessUrl in the Spring Security configuration, the user can use the redirectUrl in LoginResult to redirect instead of maintaining a returnUrl manually as in the current doc, which also doesn't work when a request cache or a defaultSuccessUrl is configured.

  • ⧉ Avoid extra events on route reinitialization. PR:10660. Ticket:10636

  • ⧉ Cannot login to authentication protected view. PR:10634

    The Vaadin security helper now has a request cache by default, which means that if a user tries to access an authentication protected view, the request will be saved and has it as a redirectUrl in the response. The logic in the login() helper didn't take this request cache into account.

  • ⧉ Avoid log an error if frontend tool can't be found. PR:10631. Ticket:9212

  • ⧉ Extract theme name from proper folder and skip generated files (#10622). PR:10647. Tickets:10451, 10544

    Extracts the custom theme name from frontend generated folder and skips theme handling when the theme generated file is being created/updated.

  • ⧉ Upper and lower case drive works in build. PR:10638. Ticket:8959

    Update the directory-maven-plugin to not fail the build on windows when the CWD drive letter is lower case.

Support

vaadin 19 is supported for one month after Vaadin 20 has been released. The latest LTS (long term support) version is Vaadin 14. More details of our release model are available on our roadmap page.

Vaadin also provides commercial support and warranty.

Getting Started with Vaadin

App starters

The best way to get started with Vaadin is to go to https://start.vaadin.com and configure your new application by setting up your views, entities, styles, and the technology stack you’re interested in.

For the full list of how to get started go to the GitHub releases.

Known Issues and Limitations

Flow

Components

Reporting Issues

We appreciate if you try to find the most relevant repository to report the issue in. If it is not obvious which project to add issues to, you are always welcome to report any issue at https://github.com/vaadin/platform/issues.

A few rules of thumb will help you and us in finding the correct repository for the issue:

1. Bug tickets and enhancement requests that are specific to a certain Vaadin component should be posted in the component's Web Component repostory (e.g. https://github.com/vaadin/vaadin-button for Button).
2. Issues that are not component-specific (e.g. requests for new components) or encompass multiple components should be posted in vaadin-flow-components repository.
3. If you encounter an issue with Flow which does not seem to be related to a specific component, the problem is likely in Flow itself. The Flow repository is https://github.com/vaadin/flow
4. If you encounter an issue with Designer, the repository is https://github.com/vaadin/designer
5. If you encounter an issue with TestBench, the repository is https://github.com/vaadin/testbench