If you don’t have a network connection, or at least a fast/reliable one, then Gradle isn’t really an option. Without a true offline mode that is. A local developer using local libraries to build a local application, from msbuild to ant and beyond has always been supported.
I know my network connection isn’t exactly spectacular, Gradle processes in Android Studio take many minutes and lock up the IDE at seemingly random times. I imagine that if I had a fast machine and a fast solid internet connection I would hardly notice them at all. Sadly I don’t think I’m in the minority. Unfortunately Google is transitioning to gradle as the build system for Android development. Things being what they are, without a true offline mode, gradle becomes a tool reserved for the well connected.
Admittedly I don’t know much about gradle at all, excepting that it appears to be the thing making Android Studio painful to use. In Android Studio there are two build.gradle files.
MyApplication directory: "
// Top-level build file where you can add configuration options common to all sub-projects/modules.
In the MyApplication/app directory: "
apply plugin: 'android'
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
compile fileTree(dir: 'libs', include: ['*.jar'])
Perhaps you can see something that says to keep going out to the internet to run gradle.
It sounds like currently there is no true offline mode for gradle. If that’s false, how can I get the IDE to use it (or what information can I point the IDE devs toward)? If it’s true, can one be added?