id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
22880	[patch] Use a single log entry for MapCSS error logging	gaben	team	"I noticed the issue when the edited MapCSS rule was invalid, see status report of #22878.

So instead

{{{
Last errors/warnings:
- 00019.987 E: Skipping to the next rule, because of an error:
- 00019.988 E: org.openstreetmap.josm.gui.mappaint.mapcss.parsergen.ParseException: Encountered "" "":"" "": """" at line 98, column 9.
}}}


{{{
Last errors/warnings:
- 00019.987 E: Skipping to the next rule, because of an error: org.openstreetmap.josm.gui.mappaint.mapcss.parsergen.ParseException: Encountered "" "":"" "": """" at line 98, column 9.
}}}
should be printed.

----

The following patch fixes the above.
{{{#!diff
Index: src/org/openstreetmap/josm/gui/mappaint/mapcss/MapCSSParser.jj
===================================================================
--- src/org/openstreetmap/josm/gui/mappaint/mapcss/MapCSSParser.jj	(revision 18702)
+++ src/org/openstreetmap/josm/gui/mappaint/mapcss/MapCSSParser.jj	(working copy)
@@ -1162,8 +1162,7 @@
         e = new ParseException(pe.getMessage()); // prevent memory leak
     }
     
-    Logging.error(""Skipping to the next rule, because of an error:"");
-    Logging.error(e);
+    Logging.error(""Skipping to the next rule, because of an error: "" + e);
     if (sheet != null) {
         sheet.logError(e);
     }
}}}"	enhancement	closed	trivial	23.04	Core		fixed	mapcss log error_handling