<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Auto-Configuration on Wim Deblauwe</title>
		<link>https://www.wimdeblauwe.com/tags/auto-configuration/</link>
		<description>Recent content in Auto-Configuration on Wim Deblauwe</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>© 2022 Wim Deblauwe</copyright>
		
		
			<lastBuildDate>Sun, 06 Sep 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.wimdeblauwe.com/tags/auto-configuration/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Testing your auto-configuration against a missing optional dependency</title>
				<link>https://www.wimdeblauwe.com/blog/2026/09/06/testing-your-auto-configuration-against-a-missing-optional-dependency/</link>
				<pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://www.wimdeblauwe.com/blog/2026/09/06/testing-your-auto-configuration-against-a-missing-optional-dependency/</guid>
				<description>&lt;div class=&#34;paragraph&#34;&gt;&#xA;&lt;p&gt;If your library or starter has optional dependencies, it is surprisingly easy to write an auto-configuration that blows up at startup for everybody who does &lt;em&gt;not&lt;/em&gt; have that optional dependency on the classpath.&#xA;Even more annoying: &lt;code&gt;FilteredClassLoader&lt;/code&gt;, the tool that Spring Boot gives us for this kind of test, cannot reproduce that failure.&#xA;In this blog post, I will show you why, and give you a small &lt;code&gt;HidingClassLoader&lt;/code&gt; that can.&lt;/p&gt;&#xA;&lt;/div&gt;</description>
			</item>
	</channel>
</rss>
