uses-library tag in AndroidManifest.xml vs useLibrary in Gradle

Question

I want to build a project, that uses Apache HTTP client, for Android P. As far as I understand, there are 2 ways to do this:

First via AndroidManifest.xml:

 <application
     ...
     <uses-library
         android:name="org.apache.http.legacy"
         android:required="false" />
 </application>

Second via build.gradle:

android {
    useLibrary 'org.apache.http.legacy'
}

Are these ways equivalent?

Why android.useLibrary command in build gradle DOES NOT add the uses-library tag in AndroidManifest.xml?

"I want to build a project, that uses Apache http client" -- use [the independent library](http://hc.apache.org/httpcomponents-client-4.3.x/android-port.html). — CommonsWare, Apr 08 '19 at 11:26

score 1 · Answer 1 · edited Jun 09 '19 at 03:21

1

Extending what CommonsWare commented.

Use gradle dependency to use apache http client, don't modify AndroidManifest.xml.

Modify your build.gradle as

dependencies {
    implementation 'org.apache.httpcomponents:httpclient-android:4.3.5.1'
}

edited Jun 09 '19 at 03:21

Rodrigo Graça

answered Apr 09 '19 at 06:21

Ranjan Kumar

2

Please explain **why** all that should be done, and try to format your answer properly – Nico Haase Apr 09 '19 at 06:49

score -1 · Answer 2 · answered Apr 09 '19 at 07:27

Adding this to AndroidManifest.xml should notify Android at runtime these classes exist:

<uses-library
      android:name="org.apache.http.legacy"
      android:required="false" />

The build.gradle declaration makes sure the library is available at compile time.

useLibrary 'org.apache.http.legacy'

2 Answers2