I was trying to figure out how to create a working JAR executable module and when debugging how nested jars for module dependencies are handled, I found that if the nested jar is not located in the correct location in its parent jar, the JarFileResourceLoader.extractJarPaths method produces an index of paths that only contains the empty path.

This seems like this almost always be an error in how the nested jar path is located.

At a minimum I would like to add some trace logging for debugging purposes. Assign it to me if you want me to look into doing this.