Bump! It'd be good to get some feedback on this sooner rather than later. On Thu, Jun 16, 2016 at 3:57 PM, julio cesar sanchez <jcesarmob...@gmail.com > wrote:
> Hi. > > I sadly can't contribute to this because I don't think I have enough > Android knowledge, but just wanted to answer on this topic as I feel that > is very important and I think this one and the previous ones you sent > related to this didn't get enough attention. > So, even if I can't personally help, maybe answering on the topic can get > some attention, or at least you can know that somebody read it and support > it. > > > 2016-06-14 22:58 GMT+02:00 Joe Bowser <bows...@gmail.com>: > > > Hey > > > > Here's a proof of concept for Android Modules. It works for cordova core > > plugins, but it's kinda brittle because I need to figure out how to > handle > > dependencies and excluding duplicate compilation in our tools. > > > > https://github.com/infil00p/cordova-android/tree/framework_fixes > > https://github.com/infil00p/cordova-plugin-inappbrowser/tree/aar_poc > > > > Surprisingly, the changes made are very minor to get this to work, and > > there's a lot of serious advantages we give. That said, our Gradle > scripts > > are incredibly brittle, and we don't have the luxury of changing any > > execution order to try to get around excluding dependencies. > > > > I think it would be good if we could add in plugin.xml a way to exclude > > compilation of dependencies that are already included. Right now if you > > include a plugin that depends on the CordovaLib module in the project, > our > > plugin will install things twice. > > > > Does anyone have any thoughts about this? I really want this to be a lot > > less brittle before introducing this method of installing plugins. > > > > Joe > > >
