Releases: vaadin/multiplatform-runtime
Vaadin Multiplatform Runtime 8.0.0-beta1
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 8) inside a Vaadin 25 (Flow) application. This is a pre-release version targeting the Vaadin 25 platform.
Multiplatform Runtime 8.0.0-beta1 is based on Flow 25.0.0-beta1, uses Jakarta EE 11, Servlet 6.1 and requires Java 21+.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
Vaadin Multiplatform Runtime 8.0.0-alpha2
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 8) inside a Vaadin 25 (Flow) application. This is a pre-release version targeting the Vaadin 25 platform.
Multiplatform Runtime 8.0.0-alpha2 is based on Flow 25.0, uses Jakarta EE 10 and Servlet 6.1 and requires Java 17.
Note that this pre-release includes only the implementation for Vaadin 8. Jakarta-compatible Vaadin 7 is under development and will be added in a further version.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
What's Changed
- feat: Upgrade to Vaadin 25 and Jakarta EE 11
- fix: remove usage of helger commons
Vaadin Multiplatform Runtime 7.1.0.alpha1
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 8) inside a Vaadin 24 (Flow) application. This is a pre-release version targeting the Vaadin 24.10 platform.
Multiplatform Runtime 7.1.0.alpha1 is based on Flow 24.10, uses Jakarta EE 9 and Servlet 5.0 and requires Java 17.
Note that this pre-release includes only the implementation for Vaadin 8. Jakarta-compatible Vaadin 7 is under development and will be added in a further versions.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
Vaadin Multiplatform Runtime 7.0.11
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 24 (Flow) application. This is a new version targeting the Vaadin 24.0+ platform.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Changes since the 7.0.10 release
- fix: store security context
- fix: Do not send has eval for navigate
- chore: bump commons-io to 2.11.0
Vaadin Multiplatform Runtime 7.0.10
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 24 (Flow) application. This is a new version targeting the Vaadin 24.0+ platform.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Changes since the 7.0.9 release
- fix: Do not write response when session is already closing (#761)
- chore: Update License file text for Commercial modules (#760)
- test: update typescript definitions (#759)
- test: Wait for target elements in tests (#758)
- chore: update typescript type definition (#757)
- test: update typescript definitions (#756)
- test: add specific class for AppShellConfiguration (#755)
- chore: bump vaadin-spreadsheet to 2.1.1
Vaadin Multiplatform Runtime 7.0.9
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 24 (Flow) application. This is a new version targeting the Vaadin 24.0+ platform.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Changes since the 7.0.8 release
- fix: Clean old LegacyEmbed when refreshing, integration test (#747)
- chore: Update cherry-pick scripts
Vaadin Multiplatform Runtime 7.0.8
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 24 (Flow) application. This is a new version targeting the Vaadin 24.0+ platform.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Changes since the 7.0.7 release
- fix: loading page when component initially hidden (#129)
Vaadin Multiplatform Runtime 7.0.7
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 24 (Flow) application. This is a new release version targeting the Vaadin 24.0+ platform.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Changes since the 7.0.6 release
- fix: Override full height for LegacyWrapper (#124)
Vaadin Multiplatform Runtime 7.0.6
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 24 (Flow) application. This is a new release version targeting the Vaadin 24.0+ platform.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Changes since the 7.0.5 release
- fix: postpone inert check for legacy component (#126)
Vaadin Multiplatform Runtime 7.0.5
The Vaadin Multiplatform Runtime (or MPR for short) allows the developer to run applications and components written with a Legacy Framework (Vaadin 7 or Vaadin 8) inside a Vaadin 24 (Flow) application. This is a new release version targeting the Vaadin 24.0+ platform.
The Multiplatform Runtime is available to all Vaadin customers in the Prime subscription tier.
The complete documentation can be found here
Changes since the 7.0.4 release
- fix: improve preserving navigation state in the url on navigation (#127)