diff --git a/docs/html/sdk/installing/index.jd b/docs/html/sdk/installing/index.jd index 85b0d130f7ea0..d8f6365888073 100644 --- a/docs/html/sdk/installing/index.jd +++ b/docs/html/sdk/installing/index.jd @@ -155,8 +155,7 @@ for your favorite IDE (if available).
If you didn't download the SDK tools, go download the SDK now, -or switch to the Eclipse ADT -install or Android Studio +or switch to the Android Studio install instructions.
diff --git a/docs/html/sdk/installing/migrate.jd b/docs/html/sdk/installing/migrate.jd index 81d6f92b0c358..696552a00ef6c 100644 --- a/docs/html/sdk/installing/migrate.jd +++ b/docs/html/sdk/installing/migrate.jd @@ -14,8 +14,8 @@ page.title=Migrating to Android Studio -If you're currently using Eclipse with ADT, we recommend you migrate to Android Studio, a new Android +
If you're currently using Eclipse with ADT, we recommend you migrate to +Android Studio, a new Android development environment powered by IntelliJ IDEA. On top of the capabilities you expect from IntelliJ, Android Studio offers:
If you still wish to get started with the ADT plugin, download and install the Eclipse ADT plugin. diff --git a/docs/html/tools/publishing/app-signing.jd b/docs/html/tools/publishing/app-signing.jd index 6e64392ea3904..4265a636a7b71 100644 --- a/docs/html/tools/publishing/app-signing.jd +++ b/docs/html/tools/publishing/app-signing.jd @@ -206,7 +206,8 @@ more than one), and enter the required information.
You can also specify your signing settings in Gradle configuration files. For more information, -see Signing settings.
+see Configuring Gradle +Builds. diff --git a/docs/html/tools/publishing/preparing.jd b/docs/html/tools/publishing/preparing.jd index b6b10fb4dd886..0b61aa7b3b676 100644 --- a/docs/html/tools/publishing/preparing.jd +++ b/docs/html/tools/publishing/preparing.jd @@ -85,7 +85,7 @@ and it is optimized with the zipalign tool. Android Studio. For example, you can use Android Studio with the Gradle build files to compile, sign, and optimize your application all at once. You can also configure the Gradle build files to do the same when you build from the command line. For more details about using the Gradle build files, see -Building Your Project with Gradle. +the Build System guide.To prepare your application for release you typically perform five main tasks (see figure 2).
Each main task may include one or more smaller tasks depending on how you are releasing your
@@ -306,15 +306,16 @@ application, see Applicatio
.apk file that is signed and optimized. The JDK includes the tools for signing the
.apk file (Keytool and Jarsigner); the Android SDK includes the tools for compiling and
optimizing the .apk file. If you are using Android Studio or you are using
-the Gradle build system from the command line, you can automate the entire build process. See
-Building Your Project with Gradle.
You can use the Gradle build system, integrated with Android Studio to build a release-ready
.apk file that is signed with your private key and optimized. To learn how to setup and
run builds from Android Studio, see
-Building Your Project with Gradle.
The build process assumes that you have a certificate and private key suitable for signing your application. If you do not have a suitable certificate and private key, diff --git a/docs/html/tools/publishing/versioning.jd b/docs/html/tools/publishing/versioning.jd index f56dbc318155a..4af6f306168fd 100644 --- a/docs/html/tools/publishing/versioning.jd +++ b/docs/html/tools/publishing/versioning.jd @@ -96,7 +96,7 @@ value for display to users.
You define both of these version attributes in the
<manifest> element of the manifest file or the Gradle build file. See
-Building Your Project with Gradle.
Here's an example manifest that shows the android:versionCode
and android:versionName attributes in the
@@ -174,4 +174,4 @@ href="{@docRoot}guide/topics/manifest/uses-sdk-element.html"><uses-sdk&
manifest element documentation and the API Levels document. For
Gradle build settings, see
-Building Your Project with Gradle.