On Tue, Oct 2, 2012 at 4:45 PM, Lindley <[email protected]> wrote: > I would prefer not to make it statically linked because I am not the one > writing the plugins. Each plugin is potentially going to be on a different > branch of a repository, and I would like to code to continue working without > undue hardship when I switch branches. Different versions of the project > files specifying static dependencies on each branch is an option, but not a > good one. > > Where the classes will be loaded from is precisely the issue. DexClassLoader > can either take a jar containing a classes.dex or an apk. I mentioned both > options in the original post. I'm fairly certain I can get things working > using the jar approach, but it is inelegant in some respects. I prefer the > paradigm of installing an apk to install a plugin, and therefore I need to > figure out how to explicitly exclude certain dependencies from being > included in the apk. >
But what you didn't mention is the distribution scheme for these plugins. If they will be distributed along with the APK then perhaps it's fine, but if they're going to be sent over the network you need to be a little more careful, loading and running potentially random code isn't a good idea, though if it's checksummed.. -- 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
