On May 27, 5:08 am, [email protected] wrote: > What should happen is that the classes invoking groovy should throw a > class not found exception since i don't have the groovy jar in the > classpath yet (theres no point atm).
The current implementation of the verifier gets really testy when code depends on nonexistent classes. It throws exceptions immediately, instead of waiting until you actually try to use the nonexistent class. You can see the details of its angst by examining the log file with "logcat". The verifier behavior will change in a future release. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
