The JDK is clearly not the problem here, I don't know what he's talking about as there are several causes that can trigger a VerifyError but in this discussion we deal with the latest ADT Eclipse plugin release. The problem here is that the ADT plugin tries to upload the referenced android projects in build path as separate APKs instead of mixing the code like in previous SDK releases. Even if several APKs are uploaded, there is no link between them on the device and so the VerifyError occurs when launching the main one. The only solution proposed so far is to use J2SE projects instead, using the android.jar in their build path (see one of my previous mail on the subject).
PS: Eclipse does not require a JDK, just a JRE, it has its own Java compiler, which compliancy level can be set based on what JRE you use. 2009/4/29 Handtwerk <d...@handtwerk.de> > > > We've had the same problem with ProSyst mBS running on cupcake. After > > some checks we found that it depends what JDK you use for building your > > jar files before DEXing them. In general here is the info: > > > > We've checked with the following JDK versions: jdk1.5.0_06, jdk1.5.0_10, > > jdk1.5.0_12, jdk1.5.0_15, jdk1.6.0_06, jdk1.6.0_10. Only with > > jdk1.5.0_06, jdk1.5.0_10 and jdk1.5.0_12 there was no verify errors. > > Can anybody confirm this? I'm developing on a Mac, facing the same > VerifyError issue. And updates 06, 10 and 12 for JDK 1.5.0 are not > available for OSX, so this would mean trouble for Android development > on OSX in general. > > Cheers, > Arne > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
