[TIMOB-27477] Android: Rebuild all native modules with gradle
GitHub Issue | n/a |
---|---|
Type | Epic |
Priority | High |
Status | Open |
Resolution | Unresolved |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Android |
Labels | 2020Q1, android, build, gradle, modules |
Reporter | Joshua Quick |
Assignee | Joshua Quick |
Created | 2019-10-17T00:13:31.000+0000 |
Updated | 2020-01-28T22:54:58.000+0000 |
Description
*Summary:*
In Titanium 9.0.0, we are changing our app/module build system to use "gradle". This build system allows us to do the following with modules:
* Build modules as
\*.aar
files. _(Self contained file containing all \*.jar
/\*.so
libraries, res files, AndroidManifest.xml, etc. that gradle can automatically merge into app for us.)_
* Provide a *.pom
XML file declaring all library dependencies the module uses. _(This solves dependency version conflicts for us, but only if all other modules do the same.)_
* Improve build times and reduces module release size. _(Dependencies are no longer bundled within module release zip and are instead downloaded via gradle/maven.)_
In particular, we want to solve the library dependency version conflicts that has been known to happen. This frequently happens when we update our "ti.playservices" libraries. We can only solve this problem if all *+native+* modules opt-in to using gradle and define their dependencies via a "build.gradle" file (ie: must agree to using same version management system).
No comments