From 5c19a842bbcc62b88a2cab604e451496e49888eb Mon Sep 17 00:00:00 2001
From: Rich Slogar <rslogar@google.com>
Date: Wed, 3 Jun 2015 13:36:07 -0700
Subject: updates: build-cmdline-update

b.android/175610

Change-Id: I712ded3e024685b35ae98f8517958db330890c18
---
 docs/html/tools/building/building-cmdline.jd | 7 -------
 1 file changed, 7 deletions(-)

(limited to 'docs/html/tools')

diff --git a/docs/html/tools/building/building-cmdline.jd b/docs/html/tools/building/building-cmdline.jd
index 33798a5..554cf59 100644
--- a/docs/html/tools/building/building-cmdline.jd
+++ b/docs/html/tools/building/building-cmdline.jd
@@ -353,13 +353,6 @@ adb -d install <em>path/to/your/app</em>.apk
   to publish your application, you <strong>must</strong> sign the application with your own private
   key, rather than the debug key generated by the SDK tools.</p>
 
-  <p>Android Studio helps you get started quickly by signing your .apk files with a debug key,
-  prior to installing them on an emulator or development device. This means that you can quickly
-  run your application from Android Studio without having to generate your own private key. No
-  specific action on your part is needed, provided ADT has access to Keytool. However, please note
-  that if you intend to publish your application, you <strong>must</strong> sign the application
-  with your own private key, rather than the debug key generated by the SDK tools.</p>
-
   <p>Please read <a href="{@docRoot}tools/publishing/app-signing.html">Signing Your
   Applications</a>, which provides a thorough guide to application signing on Android and what it
   means to you as an Android application developer. The document also includes a guide to publishing
-- 
cgit v1.1