aboutsummaryrefslogtreecommitdiff
path: root/test/transform
diff options
context:
space:
mode:
authorReinier Zwitserloot <reinier@zwitserloot.com>2012-07-16 22:51:56 +0200
committerReinier Zwitserloot <reinier@zwitserloot.com>2012-07-16 22:51:56 +0200
commitfe4985e2127e5fc54a0a1ae3c2c4fef17789f8bd (patch)
tree5274a2a3644715bb9ca644861d4b3c1f555c6b7c /test/transform
parentb1877a77be41695259108d2c755c87051b3f0d07 (diff)
downloadlombok-fe4985e2127e5fc54a0a1ae3c2c4fef17789f8bd.tar.gz
lombok-fe4985e2127e5fc54a0a1ae3c2c4fef17789f8bd.tar.bz2
lombok-fe4985e2127e5fc54a0a1ae3c2c4fef17789f8bd.zip
Added setting position of generated nodes in javac's @Synchronized as a 'pilot' to see if we cause any problems with this approach. It does generate nicer error messages!
Example: Using @Synchronized with named lock on a static method, naming a non-existent or instance lock. That used to error on line -1.
Diffstat (limited to 'test/transform')
-rw-r--r--test/transform/resource/messages-delombok/SynchronizedNameStaticToInstanceRef.java.messages2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/transform/resource/messages-delombok/SynchronizedNameStaticToInstanceRef.java.messages b/test/transform/resource/messages-delombok/SynchronizedNameStaticToInstanceRef.java.messages
index 1a084653..84336ebb 100644
--- a/test/transform/resource/messages-delombok/SynchronizedNameStaticToInstanceRef.java.messages
+++ b/test/transform/resource/messages-delombok/SynchronizedNameStaticToInstanceRef.java.messages
@@ -1 +1 @@
--1:-1 ERROR non-static variable read cannot be referenced from a static context
+5:9 ERROR non-static variable read cannot be referenced from a static context \ No newline at end of file