On Sat, Mar 24, 2012 at 8:47 AM, Boris Burtin <[email protected]> wrote: > After upgrading from R16 to R17, I started getting > NoClassDefFoundErrors for classes in dependent jarfiles. I eventually > figured out that only the jarfiles that were marked as exported were > being added to the apk. Is this intentional? Seems odd that my code > compiles in Eclipse, but then fails to run on the device unless I > check the "exported" box. >
Yes, it is intentional, and documented. Jars under libs/ are automatically exported, all other you need to set as exported. If you thing of 'exported' as 'added to classes.dex', it does make sense. http://tools.android.com/recent/dealingwithdependenciesinandroidprojects (there might be a more 'official' doc as well) -- 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
