Fix MemberResolver.lookupMethod bug when super class has more precise match

When onlyExact=false and super class have a more precise match,
it should not return with current class's maybe result.

New added testSuperCall reveals the problem.

1 files changed, 38 insertions, 0 deletions

diff --git a/src/test/javassist/SuperCallCase.java b/src/test/javassist/SuperCallCase.java
new file mode 100644
index 00000000..8d5ea9e7
--- /dev/null
+++ b/src/test/javassist/SuperCallCase.java
@@ -0,0 +1,38 @@
+package javassist;
+
+class Animal {
+}
+
+class Bear extends Animal {
+}
+
+
+/**
+ * Base class has a method with precise type.
+ */
+class Man {
+    String feed(Bear bear) {
+        return "Man feed(Bear)";
+    }
+}
+
+/**
+ * Derived class has a method which has same name with base class's and more imprecise type.
+ */
+class Keeper extends Man {
+    String feed(Animal animal) {
+        return "Keeper feed(Animal)";
+    }
+}
+
+/**
+ * Derived class has a method which call super method with precise type.
+ */
+class BearKeeper extends Keeper {
+    public BearKeeper() {
+    }
+
+    String javacResult() {
+        return super.feed(new Bear());
+    }
+}