Provide problematic config file when erroring on legacy config check. Fixes #735

Author: TBlueF

common/src/main/java/de/bluecolored/bluemap/common/config/BlueMapConfigManager.java

@@ -310,9 +310,15 @@ private Map<String, MapConfig> loadMapConfigs(Collection<ServerWorld> autoConfig
                             "To resolve this issue, rename this file to something else.");
                 }
 
-                MapConfig mapConfig = configManager.loadConfig(configFile, MapConfig.class);
-                mapConfig.checkLegacy();
-                mapConfigs.put(id, mapConfig);
+                try {
+                    MapConfig mapConfig = configManager.loadConfig(configFile, MapConfig.class);
+                    mapConfig.checkLegacy();
+                    mapConfigs.put(id, mapConfig);
+                } catch (ConfigurationException ex) {
+                    throw new ConfigurationException("Failed to load map-config:\n" +
+                            configFile.toAbsolutePath().normalize(),
+                            ex);
+                }
             }
         } catch (IOException ex) {
             throw new ConfigurationException("BlueMap failed to read your map configuration from\n" +

common/src/main/java/de/bluecolored/bluemap/common/config/ConfigurationException.java

@@ -79,7 +79,7 @@ public String getFullExplanation() {
     public String getFormattedExplanation() {
         String indentedExplanation = " " + getFullExplanation().replace("\n", "\n ");
         return "\n" + FORMATTING_BAR +
-               "\n There is a problem with your BlueMap setup!\n" +
+               "\n There is a problem with your BlueMap setup!\n\n" +
                indentedExplanation +
                "\n" + FORMATTING_BAR;
     }