Gotcha. So the problem is that other people are including it in their client libraries as well.
Would making this a library project fix the issue then? Is that your proposal? Sounds fine to me. Would just need to update the project template. On Wed, Jun 4, 2014 at 4:27 PM, Joe Bowser <[email protected]> wrote: > This is the problem with it: > > > http://stackoverflow.com/questions/23446603/conversion-to-dalvik-format-failed-unable-to-execute-dex-multiple-dex-files-de > > We have to play nice with every other Android library out there. It > doesn't mean we have to start using Gradle and enter that pile of fail > (yet), but it does mean that we have to have a way for devs to manage > their dependencies in a relatively sane way. That means if it makes > sense, you should be able to resolve this without having to delete > source from the src directory. I basically want to take a nasty hack > and replace it with a less nasty hack if possible, since Android has > problems with library dependencies. > > We shouldn't make this a plugin, because it's required by > CordovaResourceApi, which is now core, and isn't going away any time > soon. > > On Wed, Jun 4, 2014 at 1:18 PM, Andrew Grieve <[email protected]> > wrote: > > What is the problem with it? And would moving it to library project fix > the > > problem at all (or do you mean make it a plugin?). > > > > > > On Wed, Jun 4, 2014 at 2:57 PM, Joe Bowser <[email protected]> wrote: > > > >> So, recently I've heard from Greg from Untappd that he was in > >> dependency hell. So, I'm wondering about whether we can move to using > >> okhttp as an external library so that we don't have to worry about > >> licensing or redistributing this code. How do people want to do this? > >> > >> Any thoughts? > >> > >> Joe > >> >
