From b26d21b5b4893372748c55056494fb297bdc237d Mon Sep 17 00:00:00 2001
From: Adarsh Fernando
Date: Fri, 8 Apr 2016 13:56:49 -0700
Subject: [PATCH] Docs: Android Plugin DSL Ref 2.0.0 was just published. Added
some useful links.
Change-Id: Ib7657afaedf988af89969491266c1a72e91b3f5c
---
docs/html/tools/building/building-studio.jd | 26 +++++++++++++--------
docs/html/tools/revisions/gradle-plugin.jd | 22 +++++++++++------
2 files changed, 31 insertions(+), 17 deletions(-)
diff --git a/docs/html/tools/building/building-studio.jd b/docs/html/tools/building/building-studio.jd
index 8da70c0b9cb5e..7ba716fc3f424 100644
--- a/docs/html/tools/building/building-studio.jd
+++ b/docs/html/tools/building/building-studio.jd
@@ -548,21 +548,25 @@ parent.link=index.html
When you deploy a clean build, Android Studio instruments your app to allow
Instant Run to push code and resource updates. Although updating the running
app happens much more quickly, the first build may take longer to complete.
- You can improve the build process by configuring a few DEX options, such as
- maxProcessCount and javaMaxHeapSize.
+ You can improve the build process by configuring a few
+ DexOptions settings:
-
-
maxProcessCount
+
+ maxProcessCount
-
- Sets the maximum number of DEX processes that can be started
- concurrently. If the Gradle daemon is already running, you need to
- stop the process before initializing it with a new maximum process count.
- You can terminate the Gradle daemon by calling one of the following from
- the Terminal window:
+ Sets the maximum number of DEX processes that can be started concurrently.
+ If the Gradle daemon is already running, you need to stop the process
+ before initializing it with a new maximum process count. You can terminate
+ the Gradle daemon by calling one of the following from the
+ Terminal window:
- On Windows, call
gradlew --stop
@@ -573,7 +577,9 @@ parent.link=index.html
-
-
javaMaxHeapSize
+
+ javaMaxHeapSize
-
@@ -593,7 +599,7 @@ parent.link=index.html
android {
...
dexOptions {
- maxProcessCount 4
+ maxProcessCount 4 // this is the default value
javaMaxHeapSize "2g"
}
}
diff --git a/docs/html/tools/revisions/gradle-plugin.jd b/docs/html/tools/revisions/gradle-plugin.jd
index 9d688d85c4fca..20492f7d0c075 100644
--- a/docs/html/tools/revisions/gradle-plugin.jd
+++ b/docs/html/tools/revisions/gradle-plugin.jd
@@ -28,14 +28,20 @@ page.title=Android Plugin for Gradle Release Notes
+ -
+ Android Plugin DSL
+ Reference
+
+
-
Build System
Overview
-
- Android
- Plugin for Gradle
+ Android Plugin
+ for Gradle
@@ -166,15 +172,17 @@ distributionUrl = https\://services.gradle.org/distributions/gradle-2.10-all.zip
connected device.
- - Added
maxProcessCount to control how many slave dex processes can
- be spawned concurrently. The following code, in the module-level
+ - Added
+
maxProcessCount to control how many slave dex processes can be
+ spawned concurrently. The following code, in the module-level
build.gradle file, sets the maximum number of concurrent processes
to 4:
android {
...
dexOptions {
- maxProcessCount = 4
+ maxProcessCount = 4 // this is the default value
}
}
@@ -192,11 +200,11 @@ android {
...
buildTypes {
debug {
- minifyEnabed true
+ minifyEnabled true
useProguard false
}
release {
- minifyEnabed true
+ minifyEnabled true
useProguard true // this is a default setting
}
}