github vaadin/platform 19.0.7
Vaadin 19.0.7
on GitHub

latest releases: 24.4.0.beta1, 24.4.0.alpha25, 23.3.34...
2 years ago

Vaadin 19.0.7

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.8)

  • Fixes:

    • ⧉ Upgrade to LitElement 2.5.1 and lit-html 1.4.1 (#10912). PR:10919

    • ⧉ Watch component folders in parent themes (#10834). PR:10883. Ticket:9948

      Adds parent themes component folders to be watched by webpack.

    • ⧉ Upgrade to LitElement 2.5.0 and lit-html 1.4.0 (#10874) (CP: 6.0). PR:10879. Ticket:10826

    • ⧉ Preserve internal JS UI state properly (#10823) (CP: 6.0). PR:10838. Ticket:10757

    • ⧉ Use global node and tools if they are available first (#10753). PR:10769. Ticket:9863

    • ⧉ Warn to delete component CSS with theme generated in one run (#10779). PR:10828. Ticket:9948

      Workaround for #9948. Warn devs to delete component CSS file along with theme generated file in one run to avoid webpack compilation errors and application restart. (cherry picked from commit e33ec10fd591251fae6c26fcd05b358a1da053e4)

    • ⧉ Flow-client build fixed for Windows (#10815). PR:10819

    • ⧉ Extend and clarify valid tag names in LitTemplate or other elements (#10801). PR:10803. Ticket:9669

    • ⧉ Don't publish flow-client TS sources separately in JAR (#10765). PR:10795

      Improve performance of webpack build by only shipping precompiled JS of the flow-frontend TS sources, so webpack doesn't try to use the TS source files which is slower than using JS directly. The TS sources are still included in the sourcemaps (.js.map). This is a cherry-pick of 0476cd4bd7ef7c237a35e3c32aa9603903302bbb (from master to 6.0).

    • ⧉ Avoid ConcurrentModificationException in Binder (#10793). PR:10796. Ticket:9217

    • ⧉ Don't update bean property which is read-only bound (#10768). PR:10781. Ticket:9446

Vaadin Components (19.0.7)

  • Changes in all components

  • Fixes:

    • ⧉ Use bnd-maven-plugin for building OSGi (Thanks @stbischof for the contribution )(#896)(#932)(CP 19.0). PR:941.

      fix/ignore bnd issue when generating war

    • ⧉ Use bnd-maven-plugin for building OSGi (in behalf of @stbischof). PR:896

    • ⧉ Bnd export should only export project package

      PR #708 did not adress the fact that bnd exports all classes from the classpath. felix only uses the project sources this could be fixed by explicit name the the exported package bnd caclulates variables like the exported packagename remove build-helper-maven-plugin and maven project.properties rename packages that all demo projects uses the package pattern .demo bnd-plugin exists in demo project but the generates MANIFEST.MF was not used configure maven-jar-plugin that the bnd-generated MANIFEST.MF is used configure bnd to calculate the package and bsn for demo-projects changes on flow-component and demo: use bnd-maven-plugin not felix:maven-bundle-plugin run bnd-maven-plugin with default build profile

    • ⧉ Use bnd-maven-plugin in pro components. PR:932

Changes in vaadin-charts-flow

  • Fixes:

    • ⧉ Change how setSeries converts array to ArrayList. PR:946. Ticket:515

      Because setSeries(...series) uses Arrays.asList to convert from array to List, one cannot call addSeries after calling setSeries(...series) since it throws a UnsupportedOperationException. cherry-pick: #927

Changes in vaadin-date-picker-flow

- [⧉](https://github.com/vaadin/vaadin-flow-components/commit/3021da1) Set locale in onAttach instead of constructor (#167). **PR:**[843](https://github.com/vaadin/vaadin-flow-components/pull/843). **Ticket:**[262](https://github.com/vaadin/vaadin-date-picker-flow/issues/262)

Changes in vaadin-grid-flow

  • Warranty Fixes:

    • ⧉ Prevent IllegalArgumentException when sortable columns are removed and recreated(#468)(#918) (CP 19.0). PR:931. Ticket:1969

  • Fixes:

    • ⧉ Use bnd-maven-plugin in pro components. PR:932

    • ⧉ Use bnd-maven-plugin in pro components

    • ⧉ Restore sorting indicators after column order change (#876). PR:923

    • ⧉ Ensure editor closing when page refreshed while using PreserveOnRefresh (#865). PR:891. Ticket:2176

      If Editor is not closed on detach and preserve on refresh is used, the ghost editor will cause an exception.

    • ⧉ Synchronize column width recalculation with data refresh (#846). PR:872

Vaadin Multiplatform Runtime (Prime) (5.0.1)

Webcomponent versions in 19.0.6

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
Check out latest releases or
releases around vaadin/platform 19.0.7

Don't miss a new platform release

NewReleases is sending notifications on new releases.

Get notifications