This leads to 3x4x3x2 possible combinations. However, for each assembly step, only one value of each flavor group and build type can be selected, leading to an ordered list of possible manifest files that overrides the main manifest file.įor instance, the following FlavorGroups: abi, density, API, Prod/Internal leads to the following matrix of possible flavors : The rules for merging depend on each node type and can be altered using “tools:” namespace attributes.īecause of multiple product flavors and build types there can be a matrix of possible manifest files to merge. Then, manifest files of types (3) are usually merged into the resulting main manifest from previous step. Manifest files of types (1) are usually overriding the main manifest content since it’s specializing the application for a particular delivery. Product flavors and build types specific manifest files. In general, there are three types of manifest files that need to be merged into a single resulting app manifest, here in priority order : This document describes the new manifest merger tool. 5.2 Remove an attribute coming from the library. 5.1 Override an attribute coming from a library.3.9.4 List of element merging policy and key.3.4 Generic description of merging strategies.3 Elements and Attributes merging process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |