diff --git a/docs/html/tools/building/building-cmdline.jd b/docs/html/tools/building/building-cmdline.jd index 33798a5218215..0e4c8b2631e1a 100644 --- a/docs/html/tools/building/building-cmdline.jd +++ b/docs/html/tools/building/building-cmdline.jd @@ -43,7 +43,7 @@ parent.link=index.html
Whether you're building with the debug or release build type, you need to run
and build your module. This will create the .apk file that you can install on an emulator or device.
When you build using the debug build type, the .apk file is automatically signed by the SDK tools
- with a debug key based on the debuggable true setting in the module's gradle.build file,
+ with a debug key based on the debuggable true setting in the module's build.gradle file,
so it's instantly ready for installation onto an emulator or attached
development device. You cannot distribute an application that is signed with a debug key.
When you build using the release build type, the .apk file is unsigned, so you
@@ -174,7 +174,7 @@ $ ./gradlew assembleRelease
the build will prompt you for your keystore and alias password when you build using the release
build type and produce your final application package, which will be ready for distribution.
To specify your keystore and alias, open the module gradle.build file (found in +
To specify your keystore and alias, open the module build.gradle file (found in the root of the module directory) and add entries for {@code storeFile}, {@code storePassword}, {@code keyAlias} and {@code keyPassword}. For example:
@@ -188,7 +188,7 @@ keyAlias "MyReleaseKey"
...
android {
@@ -222,7 +222,7 @@ android {
This creates your Android application .apk file inside the module build/
directory, named <your_module_name>-release.apk. This .apk file has
- been signed with the private key specified in gradle.build file and aligned with {@code
+ been signed with the private key specified in build.gradle file and aligned with {@code
zipalign}. It's ready for installation and distribution.
Once built and signed in release mode