<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jackson on Flowing Code</title><link>https://www.flowingcode.com/en/tag/jackson/</link><description>Recent content in Jackson on Flowing Code</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 19 Dec 2025 19:09:10 +0000</lastBuildDate><atom:link href="https://www.flowingcode.com/en/tag/jackson/index.xml" rel="self" type="application/rss+xml"/><item><title>Vaadin 25: How We Solved JSON Migration</title><link>https://www.flowingcode.com/en/vaadin-25-how-we-solved-json-migration/</link><pubDate>Fri, 19 Dec 2025 18:59:32 +0000</pubDate><guid>https://www.flowingcode.com/en/vaadin-25-how-we-solved-json-migration/</guid><description>&lt;figure class="wp-block-image size-large">&lt;img alt="" class="wp-image-2201" height="576" loading="lazy" src="https://www.flowingcode.com/images/uploads/2025/12/Upgrading-Add-ons-for-Vaadin-25-How-We-Solved-JSON-Migration-2-1024x576.png" width="1024"/>&lt;/figure>
&lt;p class="wp-block-paragraph">&lt;strong>Vaadin 25&lt;/strong> was just released, and it comes with an &lt;a href="https://vaadin.com/blog/vaadin-25-0-release">interesting set of breaking changes&lt;/a> to keep us entertained and wide awake as we head into the year’s final stretch.&lt;/p>
&lt;p class="wp-block-paragraph">At &lt;strong>Flowing Code&lt;/strong> we &lt;a href="https://www.flowingcode.com/en/opensource/addons/">maintain more than 30 add-ons&lt;/a>, and most of them currently &lt;strong>support Vaadin 14, 23, and 24&lt;/strong>. As you can imagine, this makes the Vaadin 25 migration cycle a substantial effort. And &lt;strong>our goal is ambitious&lt;/strong>: keep a &lt;strong>single codebase&lt;/strong> compatible with all supported Vaadin versions, without branching off into Vaadin-25-specific releases unless absolutely necessary.&lt;/p></description></item></channel></rss>