Base Java Classes Still In The Classpath During Maven Android Build

I'm having a rather strange problem caused by both the facts that the android java implementation differs from the sun java implementation and that the base java classes are still

Solution 1:

The problem is that Maven automatically has the Oracle JDK on the classpath and that the Android jar provides alternate implementations of these and they sometimes differ. At this stage I do not know if the Maven Compiler Plugin can be told to remove the JDK from its classpath and just use the dependencies on the classpath. That would imho solve the issue.

Please create an issue in the Android Maven Plugin issue tracker and potentially investigate by asking on the Maven user or dev list.