Migration guides

We know that migrations suck. Not only developers fear the appearance of a new major version but also every product or project manager of an application, that uses 3rd party software, knows, that it can be a stressful and time consuming horror to integrate a new major version.

Unfortunately this applies also for this addon. There will be breaking changes here and there, that requires you to get back into your code and review everything. Nevertheless, we hope, that this migration guide helps you as good as possible to get a detailed insight of what has changed and what needs to be done to get you back on track.

If we missed something or anything is unclear, please ping us on GitHub. We hope, that your upgrade goes through as smoothly as possible.

Upgrading within 7.x

• 7.1 → 7.2 — client-side entry IDs (#202), auto-revert (#225), FullCalendarBuilder deprecation (#232), Entry.setEditable binary-compat caveat (#212), Delta.getYears/getMonths deprecation (#191), createCopyBasedOnChanges → getChangesAsEntry rename

Upgrading to v7 / Vaadin 25

• v6.x → v7.x — Vaadin 24 to 25. Includes a 6 ↔ 7 version mapping table so you can jump to the v7 release with the same feature set you have today.

Upgrading within 6.x

• 6.4 → 6.5 — backport of the 7.2 feature set (auto-revert, client-side entry IDs, FullCalendarBuilder deprecation, setEditable binary-compat caveat, Delta / createCopyBasedOnChanges deprecations) to Vaadin 24 / Java 17 / elemental JSON
• 6.3 → 6.4 — Vaadin 14 to 24.10 plus v7 feature backports. If your target is v7, do this hop first and then continue via the v6.x → v7.x guide.

Older upgrades

• 4.1 → 6.0 — Polymer removal, light DOM, TypeScript
• 4.0 → 4.1 — introduction of EntryProvider
• 3.x → 4.0 — UTC-based times, JsonItem, timezone handling