From c4360481251fdec0599598c24da400a8bace3247 Mon Sep 17 00:00:00 2001 From: Adriaan Moors Date: Tue, 22 Jul 2014 14:45:12 +0200 Subject: Better error message than 'bad symbolic reference'. Let's not scare people, and try to give them some advice. PS: we should really come up with a better mechanism for testing errors/warnings --- test/files/run/typetags_without_scala_reflect_typetag_lookup.scala | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'test/files/run/typetags_without_scala_reflect_typetag_lookup.scala') diff --git a/test/files/run/typetags_without_scala_reflect_typetag_lookup.scala b/test/files/run/typetags_without_scala_reflect_typetag_lookup.scala index 1fbdc62a1e..3d2b9f77be 100644 --- a/test/files/run/typetags_without_scala_reflect_typetag_lookup.scala +++ b/test/files/run/typetags_without_scala_reflect_typetag_lookup.scala @@ -36,8 +36,8 @@ object Test extends StoreReporterDirectTest { println(filteredInfos.mkString("\n")) storeReporter.infos.clear() compileApp(); - // we should get bad symbolic reference errors, because we're trying to use an implicit that can't be unpickled + // we should get "missing or invalid dependency detected" errors, because we're trying to use an implicit that can't be unpickled // but we don't know the number of these errors and their order, so I just ignore them all - println(filteredInfos.filterNot(_.msg.contains("bad symbolic reference")).mkString("\n")) + println(filteredInfos.filterNot(_.msg.contains("missing or invalid dependency detected")).mkString("\n")) } } -- cgit v1.2.3