Root cause was two android jars on the classpath...Yes it is a silly error, cant help but be a little dissapointed that this problem manifested itself like this
On Jun 3, 10:40 pm, Mark Murphy <[email protected]> wrote: > markdsievers wrote: > > Just a bump...Same situation, upgrading Android and have ended up with > > this problem. Someone in the next cubicle has the same project > > working, so will post the solution shortly... > > The error message is fairly self-explanatory in terms of what to do, > though the better answer is to not try adding classes in the java.* or > javax.* namespaces. > > In the OP's case, if I am reading their stack trace correctly, they were > trying to add java.security.cert.CertPathParameters, perhaps from Apache > Harmony, and Android's build tools will not appreciate that. In part, > that is because Android 1.5 already has an implementation of this interface. > > You can use classes pulled from Harmony, but you need to modify them > (and the code that uses them) to put them in another namespace. > > Bear in mind that if you do follow the error message's instructions and > use --core-library to attempt to get past this message, your application > may break in future versions of Android, if they happen to include the > same class you're trying to load and the implementations are not compatible. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Warescription: Three Android Books, Plus Updates, $35/Year --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
