Introduction:<\/strong><\/p>\n Gradle Build Files:<\/strong><\/p>\n To take a look at these build.gradle files, open Android Studio’s Project panel (by selecting the Project tab) and expand the Gradle Scripts folder. In our sample project, the first two items in the list are your project’s top-level and module-level build files.<\/p>\n <\/p>\n The screenshot below gives you an idea of how the Gradle Scripts folder might look for a project with multiple modules.<\/p>\n Top-Level Gradle Build File<\/strong>:<\/p>\n [code]\/\/Project-level Gradle build files use buildscript to define dependencies.\/\/ \/\/ NOTE: Do not place your application dependencies here; they belong allprojects { There are 3 main areas to this Android build file: Note:<\/strong> This only affects the code running the build, not the project. The project itself needs to declare its own repositories and dependencies.<\/p>\n allprojects { … }<\/strong> task clean<\/strong><\/p>\n Module-Level Gradle Build Files<\/strong> [code]apply plugin: ‘com.android.application’ buildTypes { \/\/ Stops the reverse engineering of your application\/\/ } dependencies { apply plugin:<\/strong><\/p>\n android { … }<\/strong><\/p>\n Other Gradle Files:<\/strong> gradle-wrapper.properties (Gradle Version)<\/strong> [code]distributionBase=GRADLE_USER_HOME zipStoreBase=GRADLE_USER_HOME<\/p>\n zipStorePath=wrapper\/dists<\/p>\n distributionUrl=https\\:\/\/services.gradle.org\/distributions\/gradle-2.2.1-all.zip<\/p>\n \/\/The URL where the correct version of Gradle should be downloaded from.\/\/ settings.gradle<\/strong> [code] gradle.properties (Project Properties)<\/strong> [code] local.properties (SDK Location)<\/strong> [code] Note<\/strong> that local.properties contains information that’s specific to the local installation of the Android SDK. This means that you shouldn’t keep this file under source control.<\/p>\n Some Important Points:<\/strong><\/p>\n [code] <strong>Flat File Repo:<\/strong> [code]apply plugin: ‘android’ defaultConfig { To solve this issue you can use ‘provided’ instead of ‘compile’. That tells the scope of dependency. It will work in compile time but will not include in apk. You can use like below code:<\/p>\n [code]dependencies { Gradle Android Studio\u00a0 Introduction: Gradle is an automated build toolkit that can integrate into lots of different environments, via plugins. Minimize Configuration Required for New Projects: Gradle has a set of default configuration settings that are automatically applied to every project you create in Android Studio. If you’re developing a project that doesn’t adhere […]<\/p>\n","protected":false},"author":892,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":4},"categories":[518,1],"tags":[4845,1511],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/31379"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/892"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=31379"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/31379\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=31379"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=31379"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=31379"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\nSupport a Wide Range of Devices<\/strong>,
\nOffer Different Versions of an App like Demo or Pro<\/strong><\/li>\n<\/ol>\n\n
\n
![\"gradle\"](\"\/blog\/wp-ttn-blog\/uploads\/2016\/01\/gradle.png\")
<\/p>\n![\"gradle1\"](\"\/blog\/wp-ttn-blog\/uploads\/2016\/01\/gradle1.png\")
<\/p>\n\n
\nbuildscript {
\nrepositories {
\n\/\/ jcenter() is a superset of mavenCentral(), it uses HTTPs to serve content, it is faster than mavenCentral() \/\/
\njcenter()
\n}
\n\/\/This file relies on the jcenter repository.\/\/
\ndependencies {
\nclasspath ‘com.android.tools.build:gradle:1.5.0’
\n\/\/Project is dependent on version 1.5.0 of the Android plugin for Gradle.\/\/<\/p>\n
\n\/\/ in the individual module build.gradle files
\n}
\n}<\/p>\n
\n\/\/Defines the dependencies required by your application.\/\/
\nrepositories {
\njcenter()
\n}
\n}
\n\/\/Application depends on the jCenter repository.\/\/
\ntask clean(type: Delete) {
\ndelete rootProject.buildDir
\n}
\n[\/code]<\/p>\n
\nbuildscript { … }<\/strong>
\nYou will notice a new closure buildscript. This is nothing to do with App Engine and is generally used to specify dependencies that the build script will need to it. In our case, this script requires the App Engine Gradle library to be present and hence we are specifying it via the normal dependency and specifying from which repository to take it.<\/p>\n\n
\nWe have the dependencies that this project source code needs to compile.<\/p>\n\n
\nIn addition to the project-level Gradle build file, each module has a Gradle build file of its own. Below is an annotated version of a basic, module-level Gradle build file.<\/p>\n
\n\/\/Since this project is an Android app, the build.gradle file utilises the Android plugin. if there is any library project then we’ll use apply plugin: ‘com.android.library’ as plugin \/\/
\nandroid {
\n\/\/ The following section configures all your project\u2019s Android-specific parameters, and tells Gradle which version of Android it should build your project with. If you\u2019ve developed Android applications before, the following should all be familiar. \/\/
\n\/\/ Signing configuration to generate signed app if you already have .jks file \/\/
\nsigningConfigs {
\nconfig {
\nkeyAlias ‘test’
\nkeyPassword ‘test123’
\nstoreFile file(‘\/home\/shivang\/Desktop\/test.jks’)
\nstorePassword ‘test123’
\n}
\n}
\ncompileSdkVersion 21
\n\/\/The API your project is targeting.\/\/
\nbuildToolsVersion "21.1.1"
\n\/\/\/\/The version of the build tools you want to use.\/\/
\ndefaultConfig {
\napplicationId "com.example.jessica.myapplication"
\n\/\/Defines your application\u2019s ID. Note, earlier versions of the Android plugin used \u2018packageName\u2019 instead of \u2018applicationID.\u2019\/\/
\n\/\/ Package name has deprecated now, application provides the facility to create multiple instance(Varient) of your app \/\/
\nminSdkVersion 16
\n\/\/The minimum API required by your project.\/\/
\ntargetSdkVersion 21
\n\/\/The version of Android you\u2019re developing your application for.\/\/
\nversionCode 1
\nversionName "1.0"
\n}<\/p>\n
\nrelease {
\n\/\/ add signing configuration for build \/\/
\nsigningConfig signingConfigs.config
\n\/\/ \u2018BuildTypes\u2019 controls how your app is built and packaged. If you want to create your own build variants, you\u2019ll need to add them to this section. \/\/
\nminifyEnabled true
\nshrinkResources true
\n\/\/ Resource shrinking is the automatic removal of resources that are unused, at build time, in the packaged app, you have to enable minifyEnabled in order to turn on code shrinking.<\/p>\n
\nproguardFiles getDefaultProguardFile(‘proguard-android.txt’), ‘proguard-rules.pro’
\n\/\/Applies the default ProGuard settings from the Android SDK.\/\/<\/p>\n
\n\/\/ Generates Different variants of app \/\/
\nproductFlavors {
\ndemo {
\napplicationId = "com.example.myapplication.demo"
\nresValue "string", "app_name", "Demo App"
\n\/\/ change the name of application according to variants of app \/\/
\n}
\nfull {
\napplicationId = "com.example.myapplication.full"
\nresValue "string", "app_name", "Full App"
\n}
\n}
\n}<\/p>\n
\n\/\/ A folder entirely dependent, All the jar file exist in libs directory will automatically included \/\/
\ncompile fileTree(dir: ‘libs’, include: [‘*.jar’])
\n\/\/ single file depends
\ncompile Files ( ‘libs \/ Android-Support-v4.jar’ )
\n\/\/ Gradle dependency that points to the wearable app module, because users cannot browse and install apps directly on the wearable. If packaged properly, when users download the handheld app, the system automatically pushes the wearable app to the paired wearable.
\nwearApp project(‘:wear’)
\n\/\/ Testing dependencies
\ntestCompile ‘junit:junit:4.12’
\n\/\/ Application format: packageName: artifactId: Version
\ncompile ‘com.android.support:appcompat-v7:23.1.1’
\ncompile ‘com.google.android.gms:play-services:8.3.0’
\ncompile ‘com.android.support:design:23.1.1’
\n\/\/ Use <a href="http:\/\/www.tothenew.com\/blog\/aar-android-archive-library-format-android\/">Android Archive<\/a> \/\/
\ncompile ‘com.kevinpelgrims.library:library:1.0.0@aar’
\n\/\/ Using the @aar notation if you want to download the dependencies, you should add, otherwise it may skip some dependencies \/\/
\ntransitive=true
\ncompile(name:’yourlibraryname’, ext:’aar’)
\n}
\n[\/code]<\/p>\n\n
\n
\nIn addition to the build.gradle files, your Gradle Scripts folder contains some other Gradle files. Most of the time you won’t have to manually edit these files as they’ll update automatically when you make any relevant changes to your project. However, it’s a good idea to understand the role these files play within your project.<\/p>\n
\nThis file allows other people to build your code, even if they don’t have Gradle installed on their machine. This file checks whether the correct version of Gradle is installed and downloads the necessary version if necessary. In our sample app,gradle-wrapper.properties contains the following:<\/p>\n
\n\/\/Determines whether the unpacked wrapper distribution should be stored in the project, or in the Gradle user home directory.\/\/
\ndistributionPath=wrapper\/dists
\n\/\/The path where the Gradle distributions required by the wrapper are unzipped.\/\/<\/p>\n
\n[\/code]<\/p>\n
\nThis file references all the modules that make up your project. Since our sample project has a single module, this file is very straightforward as you can see below.<\/p>\n
\ninclude ‘:app’
\nor
\ninclude ‘:mobile’, ‘:wear’, ‘:tv’, ‘:glass’, ‘:mylibrary’
\n[\/code]<\/p>\n
\nThis file contains configuration information for your entire project. It’s empty by default, but you can apply a wide range of properties to your project by adding them to this file.<\/p>\n
\n\/\/ Used to speed up gradle build process \/\/
\n\/\/ When configured, Gradle will run in incubating parallel mode.
\norg.gradle.parallel=true
\n\/\/ Gradle runs on the Java Virtual Machine (JVM) and uses several supporting libraries
\nthat require a non-trivial initialization time. As a result, it can sometimes seem a
\nlittle slow to start. The solution to this problem is the Gradle Daemon: a long-lived
\nbackground process that executes your builds much more quickly than would otherwise be
\nthe case. \/\/
\norg.gradle.daemon=true
\n\/\/ you can declare various configuration variables, just like Global variables you
\nalways declares while developing any app. These variables further use by
\nproject.variable_name, Like project.COMPILE_SDK_VER. Its more useful if your
\napplication have multiple module \/\/
\nCOMPILE_SDK_VER=23
\nBUILD_TOOL_VER=21.1.2
\n[\/code]<\/p>\n
\nThis file tells the Android Gradle plugin where it can find your Android SDK installation. For example:<\/p>\n
\nndk.dir=\/home\/shivang\/programFiles\/android-sdk-linux\/ndk-bundle
\nsdk.dir=\/home\/shivang\/programFiles\/android-sdk-linux
\n[\/code]<\/p>\n\n
\nrepositories {
\nmavenCentral() or Jcenter()
\n}
\nOr
\nrepositories {
\nmavenCentral name: ‘single_jar_repo’,
\nurls: "http:\/\/repo.mycompany.com\/jars"
\nmavenCentral name: ‘multi_jar_repos’,
\nurls: ["http:\/\/repo.mycompany.com\/jars1", "http:\/\/repo.mycompany.com\/jars1"]
\n}
\nOr
\nrepositories {
\nmavenRepo urls: "http:\/\/repo.mycompany.com\/maven2"
\n}<\/p>\n
\nrepositories {
\nflatDir name: ‘localRepository’,
\ndirs: ‘lib’ flatDir dirs: [‘lib1’, ‘lib2’]
\n}[\/code]<\/p>\n\n
\nandroid {
\ncompileSdkVersion 22
\nbuildToolsVersion "22.0.1"<\/p>\n
\nminSdkVersion 19
\ntargetSdkVersion 19
\nversionCode 1
\nversionName "1.0"
\n}
\nbuildTypes {
\nrelease {
\nminifyEnabled true
\nproguardFiles getDefaultProguardFile(‘proguard-android.txt’), ‘proguard-rules.txt’
\n}
\n}
\n }
\ndependencies {
\ncompile ‘com.android.support:appcompat-v7:+’
\ncompile ‘org.projectlombok:lombok:1.12.2’ }[\/code]<\/p>\n
\nprovided ‘org.projectlombok:lombok:1.12.2’
\n}[\/code]<\/p>\n","protected":false},"excerpt":{"rendered":"