Closed jaredsburrows closed 9 years ago
This is already supported and explained in a side note in the readme. Suppose you have a free
and a paid
flavor. Then you already have different source sets for your flavors. The plugin just merges several play folders into one like so:
- [src]
|
+ - [main]
| |
| + - [play]
| |
| + // texts and images used in all flavors
|
+ - [free]
| |
| + - [play]
| |
| + // texts and images used in your free flavor
|
+ - [paid]
|
+ - [play]
|
+ // texts and images used in your paid flavor
This way you can even support different sets of languages in your flavors.
So if both free
and paid
share source code
and resources
from main
, then what happens to the text? This setup only generates 2 APK
files.
Files in the flavour directories override files in the main source set just like your app resources would
Good, thank you!
Support
android.productFlavors
extension provided by theAndroid
plugin.For instance, if you have a free and paid version of the application where the descriptions vary.
Currently:
It would be nice to have:
etc...