On Thu, Dec 9, 2010 at 10:53 AM, BoD <[email protected]> wrote: > I was kind of assuming that in such cases the project classes would > take over but in my instance it seems it's not the case. Is this > behavior expected or an anomaly?
That behavior is expected. AFAIK, the project cannot override the OS's classes. > If it's the expected behavior, how should this be handled? Either stop using that JAR, or convert it to a new package. There's a utility for that floating around, though I forget the name and don't have a link -- sorry! -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.9 Available! -- 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
