AI 148183: Add missing android namespace to minSdkVersion

  BUG=1819430

Automated import of CL 148183

diff --git a/docs/html/sdk/RELEASENOTES.jd b/docs/html/sdk/RELEASENOTES.jd
index ed82b6b..db93215 100644 (file)
--- a/docs/html/sdk/RELEASENOTES.jd
+++ b/docs/html/sdk/RELEASENOTES.jd
@@ -207,7 +207,7 @@ looks like this: </p>
 
 <pre><code>&lt;manifest&gt;
   ...
-  &lt;uses-sdk minSdkVersion="2" /&gt;
+  &lt;uses-sdk android:minSdkVersion="2" /&gt;
   ...
 &lt;/manifest&gt;</code>
 </pre>
@@ -219,11 +219,11 @@ function properly on their devices, especially if it uses APIs introduced in
 Android 1.1. </p>
 
 <p>If your application uses APIs introduced in Android 1.1 but does not declare
-<code>&lt;uses-sdk minSdkVersion="2" /&gt;</code>, then it will run properly on
+<code>&lt;uses-sdk android:minSdkVersion="2" /&gt;</code>, then it will run properly on
 Android 1.1 devices but <em>not</em> on Android 1.0 devices. </p>
 
 <p>If your application does not use any new APIs introduced in Android 1.1, you
-can indicate Android 1.0 compatibility by removing <code>minSdkVersion</code> or
+can indicate Android 1.0 compatibility by removing <code>android:minSdkVersion</code> or
 setting the attribute to "1". However, before publishing your application, you
 must make sure to compile your application against the Android 1.0 system image
 (available in the Android 1.0 SDK), to ensure that it builds and functions
@@ -271,7 +271,7 @@ for authentication to the server.</p>
 <p>Developers should note that the registration service for MapView is now
 active and Google Maps is actively enforcing the Maps API Key requirement. 
 For information about how to register for a Maps API Key, see 
-<a href="{@docRoot}guide/topics/location/geo/mapkey.html">
+<a href="http://code.google.com/android/add-ons/google-apis/mapkey.html">
 Obtaining a Maps API Key</a>.</p>
 
 <p><strong>USB Drivers for Windows</strong></p>

diff --git a/docs/html/sdk/android-1.1.jd b/docs/html/sdk/android-1.1.jd
index ce75e60..8123fa8 100644 (file)
--- a/docs/html/sdk/android-1.1.jd
+++ b/docs/html/sdk/android-1.1.jd
@@ -35,17 +35,17 @@ system to correctly determine whether an application is compatible with
 the system, prior to installing the application. </p>
 
 <p>Applications indicate the lowest system API Level that they are compatible with by adding
-a value to the <code>minSdkVersion</code> attribute.
+a value to the <code>android:minSdkVersion</code> attribute.
 The value of the attribute is an integer corresponding to an API Level 
 identifier. Prior to installing an application, the system checks the value of 
-<code>minSdkVersion</code> and allows the install only
+<code>android:minSdkVersion</code> and allows the install only
 if the referenced integer is less than or equal to the API Level integer stored
 in the system itself. </p>
 
 <p>If you use the Android 1.1 system image to build an application
 compatible with Android-powered devices running the Android 1.1
 platform, you <strong style="color:red">must</strong> set the
-<code>minSdkVersion</code> attribute to "2" in order to specify that your application
+<code>android:minSdkVersion</code> attribute to "2" in order to specify that your application
 is compatible only with devices using the Android 1.1 (or greater) system image.
 </p>
 
@@ -68,14 +68,14 @@ your application will function properly on their devices, especially if
 it uses <a href="#apichange">APIs introduced in Android 1.1</a>. </p>
 
 <p>If your application uses APIs introduced in Android 1.1 but does not
-declare <code>&lt;uses-sdk minSdkVersion="2" /&gt;</code>, then it will
+declare <code>&lt;uses-sdk android:minSdkVersion="2" /&gt;</code>, then it will
 run properly on Android 1.1 devices but <em>not</em> on Android 1.0
 devices. In the latter case, the application will crash at runtime when
 it tries to use the Android 1.1 APIs.</p>
 
 <p>If your application does not use any new APIs introduced in Android
 1.1, you can indicate Android 1.0 compatibility by removing
-<code>minSdkVersion</code> or setting the attribute to "1". However,
+<code>android:minSdkVersion</code> or setting the attribute to "1". However,
 before publishing your application, you must make sure to compile your
 application against the Android 1.0 system image (available in the
 Android 1.0 SDK), to ensure that it builds and functions properly for

diff --git a/docs/html/sdk/android-1.5.jd b/docs/html/sdk/android-1.5.jd
index df52b62..addd644 100644 (file)
--- a/docs/html/sdk/android-1.5.jd
+++ b/docs/html/sdk/android-1.5.jd
@@ -38,10 +38,10 @@ the system, prior to installing the application.</p>
 <p>Applications can reference a specific API Level value in their
 manifest files, to indicate the minimum version of the Android system
 required to run the application. To reference a minimum API Level, applications 
-can add a <code>minSdkVersion</code> attribute in their manifest files.
+can add an <code>android:minSdkVersion</code> attribute in their manifest files.
 The value of the attribute is an integer corresponding to an API Level 
 identifier. Prior to installing an application, the system then checks the value of 
-<code>minSdkVersion</code> and allows the install only
+<code>android:minSdkVersion</code> and allows the install only
 if the referenced integer is less than or equal to the API Level integer stored
 in the system itself. </p>
 
@@ -51,10 +51,10 @@ general, you should compile your application against the lowest possible
 version of the platform that your application can support. After you determine 
 the lowest version, you should ensure that your application's manifest file 
 defines the API Level of the lowest compatible platform version in the 
-<code>minSdkVersion</code> attribute.
+<code>android:minSdkVersion</code> attribute.
 
 <p>After compiling your application, you should make sure to test it on the
-platform specified in the application's <code>minSdkVersion</code> attribute. To
+platform specified in the application's <code>android:minSdkVersion</code> attribute. To
 ensure forward-compatibility, you should also run the application on platforms
 using a higher API Level than that used by your application. To run your
 application against different platform versions in the emulator, you create an
@@ -76,7 +76,7 @@ attribute looks like this: </p>
 
 <pre>&lt;manifest&gt;
   ...
-  &lt;uses-sdk minSdkVersion="3" /&gt;
+  &lt;uses-sdk android:minSdkVersion="3" /&gt;
   ...
 &lt;/manifest&gt;</pre>
 
@@ -88,7 +88,7 @@ important if your application uses <a href="#apichange">APIs or system features
 introduced in Android 1.5</a>. </p>
 
 <p>If your application uses APIs introduced in Android 1.5 but does not
-declare <code>&lt;uses-sdk minSdkVersion="3" /&gt;</code>, then it will
+declare <code>&lt;uses-sdk android:minSdkVersion="3" /&gt;</code>, then it will
 run properly on Android 1.5 devices but <em>not</em> on Android 1.0
 devices. In the latter case, the application will crash at runtime when
 it tries to use the Android 1.5 APIs.</p>
@@ -108,7 +108,7 @@ new APIs introduced since Android 1.0, you can remove the attribute or
 set it to "1". However,
 before publishing your application, you must make sure to compile your
 application against the Android library that corresponds to the application's
-<code>minSdkVeresion</code> value.</p>
+<code>android:minSdkVeresion</code> value.</p>
 
 <h2 id="apps">Built-in Applications</h2>