Consumer ProGuard files should be handled better when a library module is used as a dependency in a multi-module project.

For example my-app/build.gradle contains the following dependency:

implementation project(':my-library')

One of the following should happen.

Let the APK module compile all the code and ignore the AAR Consumer ProGuard settings.
Compile the AAR code in the AAR module and then have the APK module pull in the compiled AAR code and use the Consumer ProGuard file.

Currently a hack workaround needs to be added to the consuming module in order to remove the consumer ProGaurd files.

afterEvaluate {
    // This removes the Consumer ProGuard files from being used.
    // We don't want to use them since we use project references as dependencies
    // and do all the obfuscation ourselves
    tasks.each {task ->
        if (task.name.startsWith("minify") && task.name.endsWith("WithR8")) {
            def filteredConfigurationFiles = task.configurationFiles.filter { file ->
                !file.path.contains("my-library")
            }
            task.configurationFiles.setFrom(filteredConfigurationFiles)
        }
    }
}