Just have module finder tell us the damn module name, if it fails then proceed to do our fallback of checking the manifest...

Author: RealMangorage

src/main/java/org/mangorage/bootstrap/internal/JarHandler.java

@@ -24,6 +24,7 @@ interface UnsafeRunnable {
     enum ModuleNameOrigin {
         MODULE_INFO, // Takes Highest priority
         MANIFEST,
+        MANIFEST_BUNDLE_SYMBOLIC_NAME,
         MULTI_RELEASE,
         GUESSED // Takes lowest
     }
@@ -136,6 +137,7 @@ private static Result resolveModuleName(Path jarPath) {
 
             // 2. Check MANIFEST.MF for Automatic-Module-Name
             Manifest manifest = jarFile.getManifest();
+
             if (manifest != null) {
                 String autoName = manifest.getMainAttributes()
                         .getValue("Automatic-Module-Name");
@@ -147,6 +149,18 @@ private static Result resolveModuleName(Path jarPath) {
                             jarPath
                     );
                 }
+
+                String symbolicName = manifest.getMainAttributes()
+                        .getValue("Bundle-SymbolicName");
+
+                if (symbolicName != null) {
+                    return new Result(
+                            symbolicName,
+                            ModuleNameOrigin.MANIFEST_BUNDLE_SYMBOLIC_NAME,
+                            jarPath
+                    );
+                }
+
             }
 
             // 3. Fallback: filename heuristic (aka desperation mode)