That's correct. At the moment the manifest of the library is only used to compile the resource of the library and figure out its package name, so it doesn't need to contain permissions, activities, services, etc... used by the library.
However, all projects using the library must include those in their own manifest. In the future (hopefully not too distant) we'll be able to merge the content of the library manifest so that you don't have to do it manually for all projects using the library. Xav On Wed, Jun 23, 2010 at 8:52 AM, String <[email protected]> wrote: > On Jun 23, 11:06 am, deg <[email protected]> wrote: > >> Also, what are the rules for AndroidManifest elements? >> - Does the main package or an Android library (or both) need to >> declare a uses-permission for something that happens in library code? >> - If a library implements a BroadcastReceiver should it be declared in >> its manifest, or that of the application (or both)? >> - etc. > > The library's manifest ONLY needs a <manifest> element with a > package="com.mylibrary.packagename" attribute. This isn't in the docs > AFAIK, but was stated in a post on this group by the Android platform > dev responsible for libraries. I can attest that I've done mine this > way and it works fine. > > String > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
