| commit | 863bbb6c5429fe7b80da4bbd340cc9512e9c79db | [log] [tgz] |
|---|---|---|
| author | Xavier Ducrohet <xav@google.com> | Wed Dec 04 02:40:02 2013 +0000 |
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Wed Dec 04 02:40:02 2013 +0000 |
| tree | 3ba24d466cba03b75e17ffb5064f204fdc61c9b3 | |
| parent | c22036f5b99f23fa2ff8de5fb796602e7a636a2e [diff] | |
| parent | ac055ae77a7b0c599727a38e18b872e294b15087 [diff] |
Merge "Add option to filter resources."
The official Gradle plugin to build Android applications.
The plugin adds several concepts to the Gradle DSL, all in the android extension:
release and debug. You can add additional build types.If you do not define any flavors for your product, only the values from the default config are used. Flavor settings override the default config.
From this, the plugin will add the appropriate tasks to build each combination of build type and product flavor. The plugin will also define the following source directories:
src/main/java - Java source to be included in all application variants.src/main/res - Resources to be included in all application variants.src/$BuildType/java - Java source to be included in all application variants with the given build type.src/$BuildType/res - Java source to be included in all application variants with the given build type.src/$ProductFlavor/java - Resources to be included in all application variants with the given product flavor.src/$ProductFlavor/res - Resources to be included in all application variants with the given product flavor.src/test/java - Test source to be included in all test applications.src/test$ProductFlavor/java - Test source to be include for the test application for the given product flavor.You can configure these locations by configuring the associated source set provided by the android extension.
Compile time dependencies are declared in the usual way.
Have a look at the tests/basic/build.gradle build file and other projects in tests customized/build.gradle to see the DSL in action.
android.target - required.android.defaultConfig.versionCode - defaults to that specified in src/main/AndroidManifest.xmlandroid.defaultConfig.versionName - defaults to that specified in src/main/AndroidManifest.xmlandroid.productFlavors.$flavor.packageName - defaults to that specified in src/main/AndroidManifest.xmlandroid.productFlavors.$flavor.versionCode - defaults to ${android.defaultConfig.versionCode}android.productFlavors.$flavor.versionName - defaults to ${android.defaultConfig.versionName}android.buildTypes.$type.zipAlign - defaults to true for release and false for debugandroid.sourceSets.main.java.srcDirs - defaults to src/main/javaandroid.sourceSets.main.resources.srcDirs - defaults to src/main/resandroid.sourceSets.$flavor.java.srcDirs - defaults to src/$flavor/javaandroid.sourceSets.$flavor.resources.srcDirs - defaults to src/$flavor/resandroid.sourceSets.$buildType.java.srcDirs - defaults to src/$buildType/javaandroid.sourceSets.$buildType.resources.srcDirs - defaults to src/$buildType/resandroid.sourceSets.test.java.srcDirs - defaults to src/test/javaandroid.sourceSets.test$Flavor.java.srcDirs - defaults to src/test$Flavor/javadependencies.compile - compile time dependencies for all applications.The source tree contains the following:
builder directory contains the builder library.gradle directory contains the plugin implementation.tests directory contains various test applications used both as samples and tests by the plugin build system.To build the plugin, run ./gradlew uploadArchives
To build the plugin for release, removing the SNAPSHOT from the version, run ./gradlew --init-script release.gradle <tasks>
To import the plugin into the IDE, run ./gradlew idea or ./gradlew eclipse.
To build a test application:
local.properties file to point at your local install of the Android SDK. Normally, these files would not be checked into source control, but would be generated when the project is bootstrapped.../../gradlew tasks to see the tasks that are available.You can also run these tasks:
assemble - builds all combinations of build type and product flavorassemble$BuildType - build all flavors for the given build type.assemble$ProductFlavor - build all build types for the given product flavor.assemble$ProductFlavor$BuildType - build the given application variant.install$ProductFlavor$BuildType - build and install the given application variant.For each variant (product-flavor, build-type):
build/source from resource directories (main-source-set, product-flavor-source-set, build-type-source-set)build/libsbuild/resourcesbuild/libsbuild/libs.Some other notes: