Open DavidPerezIngeniero opened 9 years ago
I'm not sure this is fixable. I'm using SnakeYaml to do the parsing, so by the time I see the parsed output, the line numbers are gone.
Another case:
org.clapper.sbt.izpack.IzPluginException: while scanning an alias; expected alphabetic or numeric character, but found but found *
at org.clapper.sbt.izpack.Util$class.izError(util.scala:87)
at org.clapper.sbt.izpack.IzPackYamlConfigParser.izError(Yaml.scala:297)
at org.clapper.sbt.izpack.IzPackYamlConfigParser.parse(Yaml.scala:333)
at org.clapper.sbt.izpack.IzPack$.org$clapper$sbt$izpack$IzPack$$createXML(IzPack.scala:261)
at org.clapper.sbt.izpack.IzPack$$anonfun$org$clapper$sbt$izpack$IzPack$$createXMLTask$1.apply(IzPack.scala:237)
at org.clapper.sbt.izpack.IzPack$$anonfun$org$clapper$sbt$izpack$IzPack$$createXMLTask$1.apply(IzPack.scala:235)
at scala.Function8$$anonfun$tupled$1.apply(Function8.scala:35)
at scala.Function8$$anonfun$tupled$1.apply(Function8.scala:34)
at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
This isn't very informative either! :-(
I lose the information of the original exception.
catch {
case e: Throwable =>
val e2 = findCorrectException(e)
if (logLevel == LogLevel.Debug)
e2.printStackTrace()
izError(e2.getMessage)
}
A message like this is not very self-explanatory:
I miss at least the line number.