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, 27 deletions

diff --git a/test/transform/resource/after-eclipse/EqualsAndHashCodeWithExistingMethods.java b/test/transform/resource/after-eclipse/EqualsAndHashCodeWithExistingMethods.java
deleted file mode 100644
index 50b219f1..00000000
--- a/test/transform/resource/after-eclipse/EqualsAndHashCodeWithExistingMethods.java
+++ /dev/null
@@ -1,27 +0,0 @@
-@lombok.EqualsAndHashCode class EqualsAndHashCodeWithExistingMethods {
-  int x;
-  EqualsAndHashCodeWithExistingMethods() {
-    super();
-  }
-  public int hashCode() {
-    return 42;
-  }
-}
-final @lombok.EqualsAndHashCode class EqualsAndHashCodeWithExistingMethods2 {
-  int x;
-  EqualsAndHashCodeWithExistingMethods2() {
-    super();
-  }
-  public boolean equals(Object other) {
-    return false;
-  }
-}
-final @lombok.EqualsAndHashCode(callSuper = true) class EqualsAndHashCodeWithExistingMethods3 extends EqualsAndHashCodeWithExistingMethods {
-  int x;
-  EqualsAndHashCodeWithExistingMethods3() {
-    super();
-  }
-  public boolean canEqual(Object other) {
-    return true;
-  }
-}
\ No newline at end of file