I use a temporary solution thanks to a comment of Raphael on the original topic (I posted twice, sorry): * LIB1 and LIB2 are now java projects * I removed the sun JRE from build path * I added android.jar instead, for SVN convenience, I added thanks to an Eclipse PATH variable (pointing on the android.jar in the platforms/ android-1.5 dir of the SDK) so that I don't have to version control the .jar (which is 3MB). The only flaw I see is that each developer must set/maintain this classpath variable in their Eclipse but according to me it was better than versioning this "huge" jar file... twice.
On 29 avr, 13:22, Daniel Janev <[email protected]> wrote: > Hi Guys, > > 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. > > I hope that this can help you. > > > > Evan JIANG wrote: > > Well, I met the same issue. > > Does anyone have any idea about this? > > > Best regards, > > On Tue, Apr 28, 2009 at 11:14 PM, Guillaume Perrot > > <[email protected]> wrote: > >> We have an application cut into 3 android projects: > >> * Project REAL (the real android project) > >> * Project LIB1 (an android project without any activity, just to make > >> android reusable classes) > >> * Project LIB2 (same as LIB1) > >> LIB1 and LIB2 are android projects rather than J2SE ones because LIB1 > >> and LIB2 use Android classes. > >> Project REAL has LIB1 and LIB2 in its project build path in Eclipse. > > >> In SDK 1.0 and 1.1, no problem at all when running the project REAL > >> from Eclipse, it mixes the code of the 3 projects and produces one big > >> APK with everything in it. > > >> But now in SDK 1.5, it installs 3 different APKs on the emulator or on > >> the phone (I tested both), and the project REAL immediately crashes > >> because of a VerifyError: it does not find a class that is in LIB1. > > >> The size of the produced APK is smaller, indeed LIB1 and LIB2 classes > >> are not in it... > >> I tried using uses-library in the manifest like google maps library > >> but it complains at installing, we have a "missing shared library" > >> error. > >> I tried adding class folders in build path, it compiles in Eclipse but > >> we still have a VerifyError. > >> Same thing if we use external class folders in build path. > > >> The only thing that worked for me was to add an eclipse folder, which > >> is in fact a symbolic link, and to make it a source folder. But that > >> solution is not convenient for us because when we share the projects > >> in SVN, the referenced paths are different for each developer. Using > >> eclipse path variables can do the trick but it is far from being > >> convenient. Indeed, if we have to reinstall Eclipse or if we move the > >> place we check out the code in our developer station we have to > >> reconfigure all these messy path variables in Eclipse. > > >> Is there a way to restore the old behavior on other android projects > >> in build path ? > > -- > > Best Regards, > Daniel > --------------------------------------------------------------- > Daniel Janev · Department Manager/Core Platform and Smart Home > ProSyst Software GmbH > 1606 Sofia, Bulgaria · Vladajska Str. 48 > Tel. +359 (0)2 952 35 81/109 · Fax +359 (0)2 953 26 17 > Mobile Phone +359 (0)888 678 670http://www.prosyst.com· [email protected] > --------------------------------------------------------------- > stay in touch with your product. > --------------------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
