Spring's classpath scanning works fine on JDK 9 for classpath resources
(archives as well directories) and also for archives on the module path.

However, it does not work for an exploded module layout, simply
because ClassLoader.getResource("mypackageroot") always returns null in
such a scenario.

Since ClassLoader.getResource("mypackageroot") works in all other
scenarios, including module jars on the module path, I wonder whether this
is accidental?

Juergen

Reply via email to