Manfred Moser wrote: > All that makes sense and is not a problem, but what if I would like to > write a bunch of tests that use org.apache.http and org.json classes > that would be supplied by android in the emulator. Could I run them > against stock apache and json jars (of which I would have to find the > corresponding version) outside of the android stack but then at > runtime just have them using the android ones.
Sure. Just as you won't use your mocks in production, you won't use your copies of the third-party JARs in production. > It boils down to "how > compatible are the packaged copies of source with upstream" in a > way.. The easiest thing, for third-party code, is just to grab the code itself out of source.android.com and use it. That won't work very well at all for "real" Android code, but for third-party libraries I would expect it to work reasonably well. Of course, your mileage may vary, past performance is no guarantee of future results, do not taunt Happy Fun Ball, etc. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Online Training: 21-25 June 2010: http://onlc.com -- 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
