title: Putting permissions to manifest of Android .aar library project
body: <p>I am developing an Android project which includes two modules where one is a library module for producing <code>.aar</code> files and another is a sample app utilising the produced <code>.aar</code> file.</p>
  
  <p>Thus, there are two <code>AndroidManifest.xml</code> files in this project. Say I am developing a Bluetooth library, so I put permissions for bluetooth in library's manifest file. By including this library <code>.aar</code> as dependency, can I omit the <code>&lt;uses-permission&gt;</code> tag in the app's manifest file? In other words, does Android app "merge" (may be not literally but semantically) its dependent <code>.aar</code> libraries' permissions?</p>
  
  <p>My experience suggests that while some permissions tend to behave as above, others demand explicit declaration in application's <code>AndroidManifest.xml</code>. I would like to know if my assumption is true, if there are any resources or documentations clearly distinguishing permissions those can reside in <code>.aar</code> library's manifest and those required to be declared in application's own manifest file.</p>
  
  <p>Thank you!</p>