From d2808d407a65da9fe1e290a83df0f0da107f0cf8 Mon Sep 17 00:00:00 2001 From: Reinier Zwitserloot Date: Thu, 25 Oct 2012 00:07:44 +0200 Subject: The testrunner now uses a different mechanism to verify correctness of produced errors and warnings (i.e. we intentionally compile code with errors in them to verify that the appropriate error or warning message is emitted when lombok is active during a compilation run of either javac or ecj) - instead of string comparisons, it's a little more complex. This to enable testing of both javac6 and javac7, even if they produce (slightly) different error output. Updated all message files in the 'expected output' directories to represent this change. --- .../messages-delombok/SynchronizedNameStaticToInstanceRef.java.messages | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test/transform/resource/messages-delombok/SynchronizedNameStaticToInstanceRef.java.messages') diff --git a/test/transform/resource/messages-delombok/SynchronizedNameStaticToInstanceRef.java.messages b/test/transform/resource/messages-delombok/SynchronizedNameStaticToInstanceRef.java.messages index 84336ebb..5d6bc958 100644 --- a/test/transform/resource/messages-delombok/SynchronizedNameStaticToInstanceRef.java.messages +++ b/test/transform/resource/messages-delombok/SynchronizedNameStaticToInstanceRef.java.messages @@ -1 +1 @@ -5:9 ERROR non-static variable read cannot be referenced from a static context \ No newline at end of file +5:9 non-static variable read cannot be referenced from a static context \ No newline at end of file -- cgit