ApiXmlAdjuster prefers JavaList over ArrayList

[jpobst]

Consider the type:

<class abstract="false" deprecated="not deprecated" extends="java.util.ArrayList" final="false" jni-extends="Ljava/util/ArrayList;" jni-signature="Landroidx/databinding/ObservableArrayList;" name="ObservableArrayList" static="false" visibility="public">
...
</class>

When ApiXmlAdjuster attempts to resolve the base type of java.util.ArrayList, there are 2 choices:

[Register("java/util/ArrayList", DoNotGenerateAcw=true)]
public class Android.Runtime.JavaList : Java.Lang.Object { ... }

[Register("java/util/ArrayList", DoNotGenerateAcw=true)]
public class Java.Util.ArrayList : Java.Util.AbstractList { ... }

Because we simply use the "first" type we come across that matches, we are using JavaList instead of ArrayList. This means when we try to resolve overrides for methods, it will not find base methods such as void clear ().

Practically this isn't that big of a deal. This affects code that removes "excess" overrides that we don't need to generate. (ie: we don't need to generate an override if it's the same as the base class's method.) The net result is just that we generate these extra unneeded methods.

Largely this is just an "unspecified" behavior that breaks comparisons with the new Java type resolver.

[jpobst]

Full list:

• Android.Runtime.JavaCollection
• Android.Runtime.JavaDictionary
• Android.Runtime.JavaList
• Android.Runtime.JavaSet