<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Migration on tsvinc</title>
		<link>https://tsvinc.dev/tags/migration/</link>
		<description>Recent content in Migration on tsvinc</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://tsvinc.dev/tags/migration/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Spring Boot 4 Keeps a Tracer With Tracing Off</title>
				<link>https://tsvinc.dev/posts/boot4-tracing-enabled-ignored/</link>
				<pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://tsvinc.dev/posts/boot4-tracing-enabled-ignored/</guid>
				<description>&lt;p&gt;Spring Boot 4.0&#39;s release notes cover it in one bullet, under Miscellaneous: &amp;quot;The property management.tracing.enabled has been renamed to management.tracing.export.enabled.&amp;quot; The old key doesn&#39;t forward to the new one. It doesn&#39;t fail startup, and in the run I have it doesn&#39;t log a word. Set it to &lt;code&gt;false&lt;/code&gt; and it binds to nothing.&lt;/p&gt;&#xA;&lt;p&gt;I found it while chasing a red test on Boot 4.1.2, and the dead key wasn&#39;t what turned the test red. The test was wrong: with the new key, the Tracer bean stays too.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The Build Was Green the Whole Time</title>
				<link>https://tsvinc.dev/posts/the-build-was-green-the-whole-time/</link>
				<pubDate>Sun, 26 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://tsvinc.dev/posts/the-build-was-green-the-whole-time/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;12:06.&lt;/strong&gt; &lt;code&gt;irc-bot&lt;/code&gt;, freshly ported from Spring Boot to Micronaut 5.0.6, is committed with fourteen passing tests.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;13:35.&lt;/strong&gt; A test I had just written fails on a class name.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;13:56.&lt;/strong&gt; A sanitiser build of the group&#39;s C IRC daemon names the line where it writes to address zero.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;19:15.&lt;/strong&gt; The bot is launched against a real IRC network for the first time. By 19:20 there are three more failures on the list.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Five failures in one afternoon. None of them broke compilation, and none of them tripped a test that existed before I went looking. They turned up because something finally ran: a proxy check, a socket, a live launch.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Upgrade Errors That Named the Wrong Layer</title>
				<link>https://tsvinc.dev/posts/every-error-named-the-wrong-layer/</link>
				<pubDate>Sun, 26 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://tsvinc.dev/posts/every-error-named-the-wrong-layer/</guid>
				<description>&lt;p&gt;A compiler error is supposed to work like an address. It names a file, a line and a symbol, and the fix lives somewhere near what it names.&lt;/p&gt;&#xA;&lt;p&gt;One morning in July, five Maven repos put that to the test. They had last been modernized in August 2025, and now all of them needed their frameworks dragged forward at once: Spring Boot 3.4.1 to 4.1.0 in two, Quarkus 3.17.4 to 3.37.4 in one, and two Micronaut projects from 3.x to 5.0.6. The JDK doing the compiling was Temurin 25.0.3. Every pom still targeted Java 17.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Five Things Spring Boot 4.1 Doesn&#39;t Tell You Until It&#39;s Too Late</title>
				<link>https://tsvinc.dev/posts/spring-boot-4-migration-gotchas/</link>
				<pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://tsvinc.dev/posts/spring-boot-4-migration-gotchas/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Update, 2026-10-19:&lt;/strong&gt; This post was written before Spring Boot 3.5&#39;s open-source support ended on June 30, 2026; the text now states that date in the past tense.&lt;/p&gt;&#xA;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;Spring Boot 3.5&#39;s open-source support ended on June 30, 2026. Boot 4.0 shipped in November on the Spring Framework 7 baseline, 4.1 is current stable. The migration guide exists and is decent. These are the things it doesn&#39;t emphasize enough — discovered porting a 28-API reactive WebFlux app to Spring Boot 4.1.0 on Java 25.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
