This issue is particularly evident when using Geode in a Spring Boot app which creates an 'über' jar containing all dependent jars.
When Geode is launched in this context, the following errors can be seen:
The problem here is in ClasspathScanLoadHelper.getClasses(). In this method we call:
However getResources() doesn't just work against the 'latest' classloader, but also considers the thread context classloader. In the case of a Spring Boot app, Spring does provide such a classloader and getResources is able to find the necessary resources CommandMarker classes. (These classes are found within a nested jar. For ex. jar:file:/Users/jdeppe/src/woddrive/WodDrive-GF-Server/target/WodDriveGFServer.jar!/lib/gemfire-core-1.0.0-incubating-SNAPSHOT.jar!/com/gemstone/gemfire/management/internal/cli/commands). This is all fine, but subsequent code doesn't consider classes (or packages) within nested jars, and in addition, when classes actually get resolved, the thread context classloader (where those resources might have come from) is not considered.