Merge "docs: Improved description of "package" attribute (manifest)." into mnc-mr-docs am: 190bf3b943

am: 19db30b

* commit '19db30bc49de27090422ad985eb69bace3aebeec':
  docs: Improved description of "package" attribute (manifest).

Change-Id: I90fa4b675592889fd9252e6bdaff24965fc48046
This commit is contained in:
Kevin Hufnagle
2016-04-26 08:50:22 +00:00
committed by android-build-merger

View File

@@ -52,10 +52,13 @@ and specify {@code xmlns:android} and {@code package} attributes.</dd>
to "{@code http://schemas.android.com/apk/res/android}".</dd> to "{@code http://schemas.android.com/apk/res/android}".</dd>
<dt><a name="package"></a>{@code package}</dt> <dt><a name="package"></a>{@code package}</dt>
<dd>A full Java-language-style package name for the application. The name should <dd>A full Java-language-style package name for the Android application. The
be unique. The name may contain uppercase or lowercase letters ('A' name should be unique. The name may contain uppercase or lowercase letters
through 'Z'), numbers, and underscores ('_'). However, individual ('A' through 'Z'), numbers, and underscores ('_'). However, individual
package name parts may only start with letters. package name parts may only start with letters. Note that you can use
different names for the Android application package and for the Java package
identifiers used in the application's classes; these two types of names are
entirely independent.
<p>To avoid conflicts with other developers, you should use Internet domain ownership as the <p>To avoid conflicts with other developers, you should use Internet domain ownership as the
basis for your package names (in reverse). For example, applications published by Google start with basis for your package names (in reverse). For example, applications published by Google start with