Update vaadin.version to v25 (major) - autoclosed #506
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
24.9.8→25.0.224.9.8→25.0.2Release Notes
vaadin/platform (com.vaadin:vaadin-maven-plugin)
v25.0.2: Vaadin 25.0.2Compare Source
This is a maintenance release for Vaadin 25.0. See 25.0.0 release notes for details and resources.
Changelogs
Official add-ons and plugins:
v25.0.0: Vaadin 25.0.0Compare Source
Upgrading · Docs · Get Started
New and Noteworthy
Supported versions
Vaadin Eclipse plugin
In addition to IntelliJ and VS Code, there is now a plug-in for Eclipse
Simplified production builds
The default in new projects is that
mvn installbuilds a production artifact without needing aproductionprofile. Projects must have an optional dependency oncom.vaadin/vaadin-dev. Optional dependencies are automatically left out of the production artifact.This works out of the box for Maven + Gradle with Spring Boot or Quarkus. For other project types, you might still need a
developmentand/orproductionprofile.New Aura theme, no material theme
There is a new Aura theme with a fresh, modern look. The Lumo theme remains as another theme option.
Components have new base styles to make it easier to create a completely custom theme.
Theme and styling changes
It is recommended that you write CSS as static files and use
@StyleSheetto load them instead of using@Themeandfrontend/themes. You can use@ColorSchemeto define dark mode.With themes as static CSS files, they can be unloaded and you can switch themes at runtime.
You can keep using
@CssImportwhich places the CSS files inside the frontend bundle but that requires a bundle build and CSS cannot be unloaded.Tailwind CSS support (experimental)
You can use Tailwind classes in your CSS and in your views once you enable to feature flag.
Components use Lit
All web components have been migrated from Polymer to Lit
Component updates
High-level component communication
When building your own components or add-ons, you can now use beans, lists, maps and other collections instead of the Elemental JSON API, which was removed.
Fewer dependencies
Many Java and Node dependencies have been removed in favor of using built-in APIs,
for example
guava,commons-(codec|compress|fileupload2|io|lang3),ph-css,swagger,gwt-elementalBoth the production JAR/WAR and the frontend bundle are smaller thanks to this.
Projects relying on these as transitive dependencies need to add them explicitly.
Offline license format change
The format of the offline license has slightly changed and you need to download a new license from vaadin.com
We have added two Maven goals:
mvn vaadin:download-licensewhich downloads your online license andmvn vaadin:download-offline-licensewhich helps you obtain an offline license.Signals (Experimental)
Convenience methods for
Elementhave been added along with a newReferenceSignaltype. High level API is still in progress.Hilla
Hilla features are bound to be integrated into Flow. In this version, Hilla has only been changed to be an opt-in dependency. Add
com.vaadin/hilla-spring-boot-starterto keep using Hilla.Miscellaneous changes
Uploads are now sent as raw data instead of multipart request, removing the need to configure size limits in many cases and providing a better user experience.
Browser details such as viewport size, timezone are available when initializing the view.
When automatically installing Node, the full Node distribution is installed in a Node version specific folder instead of overwriting an old installation.
Changelogs
Official add-ons and plugins:
Upgrading guides
Support
Vaadin 25 is the latest stable version, with extended support options available (release model).
Vaadin also provides commercial support and warranty.
Supported technologies
Any IDE or editor that works with the language of your choice should work well. Our teams often use IntelliJ, Eclipse, VS Code among others.
Vaadin IDE plugins (IntelliJ and VS Code) support the IDE versions released during the last 12 months
Vaadin Designer supports the following IDEs:
Eclipse from Photon and upwards
JetBrains IntelliJ IDEA from 2017 upwards
Vaadin Flow requires Java Servlet API 6.1 and Java 21 or newer. It is tested on:
Apache Tomcat 11
Open Liberty 23
RedHat JBoss EAP 8.1
WEB-INFfolder asjboss-deployment-structure.xmlWorkaround for supporting RedHat JBoss EAP 8.0
WildFly 36 +
WEB-INFfolder asjboss-deployment-structure.xmlWorkaround for supporting WildFly 36
Workaround for supporting WildFly 37+
Jetty 12
Payara Server 6
Payara Micro 6
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.