Android Studio Series Tutorial six--gradle multi-channel packaging

Because of the many channels in the domestic Android market, in order to count the download of each channel and other data statistics, we need to be packaged separately for each channel, if let you hit dozens of market package is not bored to death, but with Gradle, this is no longer a thing.

Friend Alliance multi-channel packaging

Needless to say, in the case of Friends of the league statistics, in Androidmanifest.xml there will be such a paragraph:

<meta-data    android:name="UMENG_CHANNEL"    android:value="Channel_ID"/>

The channel_id inside is the channel mark. Our goal is to automatically change this value at compile time.

• The first step is to configure placeholder in Androidmanifest.xml.

<meta-data    android:name="UMENG_CHANNEL"    android:value="${UMENG_CHANNEL_VALUE}"/>

• The second step is set in Build.gradle productflavors

Android {      productflavors {        Xiaomi {            manifestplaceholders = [Umeng_channel_value: "Xiaomi"]        }        _360 {            manifestplaceholders = [Umeng_channel_value: "_360"]        }        Baidu {            manifestplaceholders = [Umeng_channel_value: "Baidu"]        }        Wandoujia {            manifestplaceholders = [Umeng_channel_value: "Wandoujia"]        }    }  }

or batch Modification

 android  {   Productflavors  { xiaomi  {}  _360  {}  baidu  {}  
    
     wandoujia  
     {}  
     }  
     productflavors all  { flavor  ->  flavor   manifestplaceholders  =  [ umeng_channel_value  :   Name    }  }  
     

Very simple and clear, is there? Execute directly ./gradlew assemblerelease , then you can have a quiet cup of coffee and wait for the package to finish.

Assemble combining build variants to create a task

The previous blog describes the assemble command, which creates its own task in conjunction with the build Type , such as:

• ./gradlew Assembledebug

• ./gradlew Assemblerelease

In addition, assemble can be combined with Product Flavor to create a new task, in fact assemble is used in conjunction with Build variants , and Build Variants =build Type + Product Flavor , for example everyone understands:

If we want to pack the release version of the Wandoujia channel, it's good to do the following:

• ./gradlew Assemblewandoujiarelease

If we only play Wandoujia channel version, then:

• ./gradlew Assemblewandoujia

This command generates release and debug versions of the Wandoujia channel

In the same vein, I want to play all release versions:

• ./gradlew Assemblerelease

This command will flavor the release version of all the channels under product.

In summary, theassemble command creates a task with the following usage:

• **assemble**: Allows you to build a variant version directly, such as Assembleflavor1debug.

• **assemble**: Allows you to build all the APK for the specified build type, for example Assembledebug will build Flavor1debug and Flavor2debug two variant versions.

• **assemble**: Allows all apk to be built for the specified flavor, for example AssembleFlavor1 will build Flavor1debug and Flavor1release two variant versions.

The complete Gradle script

Finally, a great benefit, a full gradle file configuration that I used in the project:

Apply plugin: ' Com.android.application 'def Releasetime() {    return New Date().format("Yyyy-mm-dd", TimeZone.getTimeZone("UTC"))}Android {    compilesdkversion  +    buildtoolsversion ' 21.1.2 '    Defaultconfig {        ApplicationID "com.boohee.*"        minsdkversion  -        targetsdkversion  +        Versioncode 1        Versionname "1.0"                // DexBreakthrough65535The Restrictions        multidexenabled true        // default isUmengthe channel        manifestplaceholders = [Umeng_channel_value: "Umeng"]    }    lintoptions {        Abortonerror false    }    Signingconfigs {        Debug {            // No Debug Config        }        Release {            StoreFile file(".. /yourapp.keystore ")            Storepassword "Your password"            Keyalias "Your alias"            Keypassword "Your password"        }    }    Buildtypes {        Debug {            // ShowLog            Buildconfigfield "Boolean", "Log_debug", "true"            Versionnamesuffix "-debug"            minifyenabled false            zipalignenabled false            shrinkresources false            Signingconfig Signingconfigs.Debug        }        Release {            // does not displayLog            Buildconfigfield "Boolean", "Log_debug", "false"            minifyenabled true            zipalignenabled true            // Remove the uselessResourcefile            shrinkresources true            Proguardfiles Getdefaultproguardfile(' Proguard-android.txt '), ' Proguard-rules.pro '            Signingconfig Signingconfigs.Release            applicationvariants. All { Variant  -                Variant.outputs. each { Output  -                    def OutputFile = Output.OutputFile                    if (OutputFile != NULL && OutputFile.name.EndsWith('. apk ')) {                    // Outputapkname calledBOOHEE_V1.0_2015- on- the_wandoujia.apk                        def FileName = "Boohee_v${defaultconfig.versionname}_${releasetime ()}_${variant.productflavors[0].name}.apk"                        Output.OutputFile = New File(OutputFile.Parent, FileName)                    }                }            }        }    }    // Friend Alliance multi-channel packaging    productflavors {        Wandoujia {}        _360 {}        Baidu {}        Xiaomi {}        Tencent {}        Taobao {}        ...    }    productflavors. All { Flavor  -        Flavor.manifestplaceholders = [Umeng_channel_value: name]    }}Dependencies {    Compile Filetree(dir: ' Libs ', include: [' *.jar '])    Compile ' com.android.support:support-v4:21.0.3 '    Compile ' com.jakewharton:butterknife:6.0.0 '    ...}

Android Studio Series Tutorial six--gradle multi-channel packaging