<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Classpath on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/classpath/</link>
    <description>Recent content in Classpath on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/classpath/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ClassGraph vs Reflections vs Jandex in 2026: Picking a JVM Classpath Scanner That Still Works on Modern Java</title>
      <link>https://www.pistack.xyz/posts/2026-11-04-classgraph-vs-reflections-vs-jandex-jvm-classpath-scanning/</link>
      <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-04-classgraph-vs-reflections-vs-jandex-jvm-classpath-scanning/</guid>
      <description>&lt;p&gt;You add one annotation — &lt;code&gt;@Plugin&lt;/code&gt;, &lt;code&gt;@Route&lt;/code&gt;, &lt;code&gt;@Extension&lt;/code&gt; — and suddenly your framework needs to find every class that carries it. That is the moment a Java project discovers the classpath scanning problem: the JDK can tell you the superclass of a class you already have, but it cannot tell you &amp;ldquo;give me every class in this jar that implements &lt;code&gt;Plugin&lt;/code&gt;&amp;rdquo;. You either scan, or you maintain a hand-written registry that drifts out of date the first time someone adds a module.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
