Androd gradle's substitution of its use module dependency

background

We are in the process of multi module project development , There are scenes like this , The project relies on one's own or other colleagues aar modular , Sometimes for the convenience of development and debugging , Often put aar Change to local source code dependency , When the development is completed and submitted , It will be modified back to aar rely on , This will be very inconvenient , The development process is shown below ：

solve

At first we passed in app Of build.gradle Inside dependency Judge if it needs local dependency aar, Just replace it with implementation project rely on , The pseudocode is as follows ：

dependencies {
    if(enableLocalModule) {
        implementation 'custom:test:0.0.1'
    } else {
        implementation project(path: ':test')
    }
} 

This way, you don't have to modify the code back every time you submit it aar rely on , But if other modules also rely on this aar modular , There will be problems , Although you can continue to modify the dependencies in other modules , But it's invasive , And it can't completely solve the problem , Local dependencies and aar Dependent code inconsistencies .

Gradle Officials offer a better solution to this scenario DependencySubstitution, Use as follows ：

step 1： stay settting.gradle, Add the following code ：

//  Load local  module
if (file("local.properties").exists()) {
    def properties = new Properties()
    def inputStream = file("local.properties").newDataInputStream()
    properties.load( inputStream )
    def moduleName = properties.getProperty("moduleName")
    def modulePath = properties.getProperty("modulePath")
    if (moduleName != null && modulePath != null) {
        include moduleName
        project(moduleName).projectDir = file(modulePath)
    }
} 

step 2： stay app Of build.gradle Add the following code

configurations.all {
    resolutionStrategy.dependencySubstitution.all { DependencySubstitution dependency ->
        // use local module
        if (dependency.requested instanceof ModuleComponentSelector && dependency.requested.group == "custom") {
            def targetProject = findProject(":test")
            if (targetProject != null) {
                dependency.useTarget targetProject
            }
        }
    }
} 

step 3：： stay local.properties in

moduleName=:test
modulePath=../AndroidStudioProjects/TestProject/testModule 

It's done here , The follow-up only needs to be in local.properties Opening and closing , That is to say aar Module local dependency debugging , You don't have to modify the code manually aar rely on .

The end of the

In the twinkling of an eye, time really flies . We go our separate ways , They also set out on their own journey , But even if I haven't seen you for years , Because of this friendship, we are still as before “ close ”. Don't forget the beginning of the party must always . Come on! , Programmers , in my opinion 35 year ,40 Age has never been a crisis , As long as you never forget why you set foot on the journey ！

Finally, we need the same information , Sure I replied by private letter 【 Study 】 Or scan the QR code below I'd like to share it with you ！

In order to let more friends who are studying or preparing for an interview recently see this article , I hope you can comment more , give the thumbs-up + forward ！

** Thanks again to all my friends who have provided me with the topic , Thank you all the way ！