diff options
Diffstat (limited to 'docs/html/tools/publishing/preparing.jd')
-rw-r--r-- | docs/html/tools/publishing/preparing.jd | 58 |
1 files changed, 22 insertions, 36 deletions
diff --git a/docs/html/tools/publishing/preparing.jd b/docs/html/tools/publishing/preparing.jd index 5265fce..b6b10fb 100644 --- a/docs/html/tools/publishing/preparing.jd +++ b/docs/html/tools/publishing/preparing.jd @@ -82,10 +82,10 @@ and it is optimized with the zipalign tool.</p> </div> <p>The signing and optimization tasks are usually seamless if you are building your application with -Eclipse and the ADT plugin or with the Ant build script (included with the Android SDK). For -example, you can use the Eclipse Export Wizard to compile, sign, and optimize your application all -at once. You can also configure the Ant build script to do the same when you build from the command -line.</p> +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 +<a href="{@docRoot}tools/gradle/studio-build.html">Building Your Project with Gradle</a>.</p> <p>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 @@ -114,8 +114,8 @@ developer holds the private key). The Android system uses the certificate as a m the author of an application and establishing trust relationships between applications. The certificate that you use for signing does not need to be signed by a certificate authority; the Android system allows you to sign your applications with a self-signed certificate. To learn about -certificate requirements, see <a href="{@docRoot}tools/publishing/app-signing.html#cert">Obtain a -suitable private key</a>.</p> +certificate requirements, see <a href="{@docRoot}tools/publishing/app-signing.html">Signing Your +Applications</a>.</p> <p class="caution"><strong>Important:</strong> Your application must be signed with a cryptographic key whose validity period ends after 22 October 2033.</p> @@ -226,9 +226,9 @@ tasks:</p> release.</li> </ul> -<h4>Review and update your manifest settings</h4> +<h4>Review and update your manifest and Gradle build settings</h4> -<p>Verify that the following manifest items are set correctly:</p> +<p>Verify that the following manifest and build files items are set correctly:</p> <ul> <li><a href="{@docRoot}guide/topics/manifest/uses-permission-element.html"> @@ -248,7 +248,7 @@ tasks:</p> </li> </ul> -<p>There are several additional manifest elements that you can set if you are releasing your +<p>There are several additional manifest or build file elements that you can set if you are releasing your application on Google Play. For example, the <code>android:minSdkVersion</code> and <code>android:targetSdkVersion</code> attributes, which are located in the <a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html"> <uses-sdk></a> element. For more @@ -303,38 +303,24 @@ application, see <a href="{@docRoot}google/play/licensing/index.html">Applicatio <h2 id="publishing-build">Building Your Application for Release</h2> <p>After you finish configuring your application you can build it into a release-ready -<code>.apk</code> fle that is signed and optimized. The JDK includes the tools for signing the +<code>.apk</code> file that is signed and optimized. The JDK includes the tools for signing the <code>.apk</code> file (Keytool and Jarsigner); the Android SDK includes the tools for compiling and -optimizing the <code>.apk</code> file. If you are using Eclipse with the ADT plugin or you are using -the Ant build script from the command line, you can automate the entire build process.</p> +optimizing the <code>.apk</code> 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 +<a href="{@docRoot}tools/gradle/studio-build.html">Building Your Project with Gradle</a>.</p> -<h3>Building with Eclipse</h3> +<h3>Building with Android Studio</h3> -<p>You can use the Eclipse Export Wizard to build a release-ready <code>.apk</code> file that is -signed with your private key and optimized. To learn how to run the Export Wizard, see -<a href="{@docRoot}tools/publishing/app-signing.html#ExportWizard">Compile and sign with Eclipse -ADT</a>. The Export Wizard compiles your application for release, signs your application with your -private key, and optimizes your application with the zipalign tool. The Export Wizard should run -successfully if you have run or debugged your application from Eclipse and you have no errors in -your application (see <a href="{@docRoot}tools/building/building-eclipse.html">Building -and Running from Eclipse with ADT</a> for more information.</p> +<p>You can use the Gradle build system, integrated with Android Studio to build a release-ready +<code>.apk</code> file that is signed with your private key and optimized. To learn how to setup and +run builds from Android Studio, see +<a href="{@docRoot}tools/gradle/studio-build.html">Building Your Project with Gradle</a>.</p> -<p>The Export Wizard assumes that you have a <a href="#billing-keys">certificate and private key</a> +<p>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, -the Export Wizard will help you generate one (see -<a href="{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a> for more -information about the signing process and signing guidelines.</p> - -<h3>Building with Ant</h3> - -<p>You can use the Ant build script (included in the Android SDK) to build a release-ready -<code>.apk</code> file that is signed with your private key and optimized. To learn how to do this, -see <a href="{@docRoot}tools/building/building-cmdline.html#ReleaseMode">Building in -Release Mode</a>. This build method assumes you have a <a href="#billing-keys">certificate and -private key</a> suitable for signing your application. If you do not have a suitable certificate and -private key, the Export Wizard will help you generate one (see -<a href="{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a> for more -information about the signing process and signing guidelines.</p> +Android Studio can help you generate one. For more information about the signing process, see +<a href="{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>.</p> + <h2 id="publishing-resources">Preparing External Servers and Resources</h2> |