Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 8998fe68 authored by Kevin Hufnagle's avatar Kevin Hufnagle
Browse files

docs: Improved description of "package" attribute (manifest). 

The description of the "package" attribute for an Android
application's <manifest> element now states more clearly that the
Android package name and the Java package name(s) used in the app's
classes do not need to be the same.

Bug: 2735276
Change-Id: Ifa30615c1cca5f6f19e4d1d0c071e4e256b3151b
parent 19383525

docs/html/guide/topics/manifest/manifest-element.jd

+19 −16
Original line number Diff line number Diff line
@@ -52,10 +52,13 @@ and specify {@code xmlns:android} and {@code package} attributes.</dd> 
to "{@code http://schemas.android.com/apk/res/android}".</dd>



<dt><a name="package"></a>{@code package}</dt>

<dd>A full Java-language-style package name for the application.  The name should 

be unique.  The name may contain uppercase or lowercase letters ('A'

through 'Z'), numbers, and underscores ('_').  However, individual

package name parts may only start with letters.

<dd>A full Java-language-style package name for the Android application. The

  name should be unique.  The name may contain uppercase or lowercase letters

  ('A' through 'Z'), numbers, and underscores ('_').  However, individual

  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

basis for your package names (in reverse). For example, applications published by Google start with