ecj tests and eclipse tests are now effectively doing the same thing, except the ecj tests are written in a slightly more close-to-reality way, and do work for 'val'. eclipse test aspect removed.

1 files changed, 0 insertions, 36 deletions

diff --git a/test/transform/resource/after-eclipse/SynchronizedName.java b/test/transform/resource/after-eclipse/SynchronizedName.java
deleted file mode 100644
index a7edd3e7..00000000
--- a/test/transform/resource/after-eclipse/SynchronizedName.java
+++ /dev/null
@@ -1,36 +0,0 @@
-class SynchronizedName {
-  private Object read = new Object();
-  private static Object READ = new Object();
-  <clinit>() {
-  }
-  SynchronizedName() {
-    super();
-  }
-  @lombok.Synchronized("read") void test1() {
-    synchronized (this.read)
-      {
-        System.out.println("one");
-      }
-  }
-  @lombok.Synchronized("write") void test2() {
-    System.out.println("two");
-  }
-  static @lombok.Synchronized("read") void test3() {
-    synchronized (SynchronizedName.read)
-      {
-        System.out.println("three");
-      }
-  }
-  @lombok.Synchronized("READ") void test4() {
-    synchronized (this.READ)
-      {
-        System.out.println("four");
-      }
-  }
-  @lombok.Synchronized(value = "read") void test5() {
-    synchronized (this.read)
-      {
-        System.out.println("five");
-      }
-  }
-}
\ No newline at end of file