Don't report synthetic erased bridge methods (e.g. apply) #36

The correctly typed apply method is already reported so don't report the erased method as well.

Author: bantonsson

reporter/functional-tests/src/test/case-class-concrete-becomes-abstract-nok/problems.txt

@@ -1,4 +1,3 @@
 class A was concrete; is declared abstract in new version
-method apply()java.lang.Object in object A does not have a correspondent in new version
 method apply()A in object A does not have a correspondent in new version
 the type hierarchy of object A has changed in new version. Missing types {scala.runtime.AbstractFunction0}

reporter/src/main/scala/com/typesafe/tools/mima/lib/analyze/method/MethodChecker.scala

@@ -37,7 +37,7 @@ private[analyze] abstract class BaseMethodChecker extends Checker[MemberInfo, Cl
 
 private[analyze] class ClassMethodChecker extends BaseMethodChecker {
   def check(method: MemberInfo, inclazz: ClassInfo): Option[Problem] = {
-    if (method.nonBridge && method.nonAccessible)
+    if (method.nonAccessible)
       None
     else if (method.isDeferred)
       super.check(method, inclazz.lookupMethods(method.bytecodeName))
@@ -48,7 +48,7 @@ private[analyze] class ClassMethodChecker extends BaseMethodChecker {
 
 private[analyze] class TraitMethodChecker extends BaseMethodChecker {
   def check(method: MemberInfo, inclazz: ClassInfo): Option[Problem] = {
-    if (method.nonBridge && method.nonAccessible)
+    if (method.nonAccessible)
       None
     else if (method.owner.hasStaticImpl(method))
       checkStaticImplMethod(method, inclazz)