Gradle remove dependency demo

//1. Directly rely on third-party open source libraries, usually hosted in jitpack or jcenterimplementation 'com.google.code.gson:gson:2.2.4'implementation 'com.android.support:cardview-v7:25.0.0'implementation 'com.android.support:design:25.0.0'//2. Directly rely on the local aar file, usually in the libs directoryimplementation(name: 'LiteAVSDK_Professional_5.1.5293', ext: 'aar')//3. Directly depend on the local jar fileimplementation files('libs/bdasr_V3_20170801_60da871.jar')//4. Depend on the local modelimplementation project(':wavelibrary')implementation project(':android-ffmpeg')

Library project dependency delivery problem

1. Commonly used basic types of dependencies are: provided and compile. Provided will not be packaged into apk or aar only when the compilation takes effect; compile will be packaged into apk or aar (if it is a library project, there are special cases,Refer to 3 below).

2. The current (compile+) dependencies of the app project will be packaged into the app

3. In the library project:

1) jar package: remote dependencies will not be packaged into aar; local dependencies will;

2) aar: Neither remote nor local will be packaged into aar.

3) If you want to provide the aar of your library project to others, you need to tell him other aars and remote jar packages that the library project depends on (because they are not packaged into aar)

4) If the dependency is passed through the project (ie compile project(':lib')), the dependency can be passed, so there is no need to declare the dependency once.

Remove duplicate dependencies

1. The third-party library also uses the same library for implementation or compile dependencies

 implementation('com.allenliu.versionchecklib:library:2.0.5') {exclude group: 'com.android.support', module: 'appcompat-v7'exclude group: 'com.android.support.constraint', module: 'constraint-layout'exclude group: 'org.greenrobot', module: 'eventbus'exclude group: 'com.squareup.okhttp3', module: 'okhttp'}