Question

我无法创建两种使用不同清单的不同构建类型。即使在使用--rerun-tasks重新运行gradle并完全删除构建目录之后，包含在apk中的AndroidManifest也是不正确的。例如，我运行assembleRelease，它包括ReleasePlus构建类型中的AndroidManifest。我想保持项目结构的原样，而不必切换到新的src // *结构。我也尝试过使用产品口味，但如果不改变结构，这似乎不太可能。

的build.gradle：

buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:0.6.+'
    }
}
apply plugin: 'android'

dependencies {
    compile fileTree(dir: 'libs', include: '*.jar')
}

android {
    compileSdkVersion 18
    buildToolsVersion "17.0.0"

    sourceSets {
        main {
            manifest.srcFile 'AndroidManifest.xml'
            java.srcDirs = ['src']
            resources.srcDirs = ['src']
            aidl.srcDirs = ['src']
            renderscript.srcDirs = ['src']
            res.srcDirs = ['res']
            assets.srcDirs = ['assets']
        }

        // Move the tests to tests/java, tests/res, etc...
        instrumentTest.setRoot('tests')

        // Move the build types to build-types/<type>
        // For instance, build-types/debug/java, build-types/debug/AndroidManifest.xml, ...
        // This moves them out of them default location under src/<type>/... which would
        // conflict with src/ being used by the main source set.
        // Adding new build types or product flavors should be accompanied
        // by a similar customization.
        debug.setRoot('build-types/debug')
        release.setRoot('build-types/release')
    }

    signingConfigs {
        myConfig {
            storeFile file("app.keystore")
            ...
        }
    }

    buildTypes {
        release {
            runProguard true
            proguardFile 'proguard.flags'
            signingConfig signingConfigs.myConfig
            buildConfig 'public final static boolean PLUS = false; public final static String PROVIDER_AUTHORITY = "com.app.settings";'
        }
        debug {
            buildConfig 'public final static boolean PLUS = false; public final static String PROVIDER_AUTHORITY = "com.app.settings";'
        }
        debugPlus.initWith(buildTypes.debug)
        debugPlus {
            packageNameSuffix '.plus'
            buildConfig 'public final static boolean PLUS = true; public final static String PROVIDER_AUTHORITY = "com.app.plus.settings";'
            sourceSets {
                main {
                    manifest.srcFile 'AndroidManifestPlus.xml'
                    java.srcDirs = ['src', 'src-plus']
                    res.srcDirs = ['res', 'res-plus']
                }
                debugPlus.setRoot('build-types/debugPlus')
            }
        }
        releasePlus.initWith(buildTypes.release)
        releasePlus {
            packageNameSuffix '.plus'
            buildConfig 'public final static boolean PLUS = true; public final static String PROVIDER_AUTHORITY = "com.app.plus.settings";'
            sourceSets {
                main {
                    manifest.srcFile 'AndroidManifestPlus.xml'
                    java.srcDirs = ['src', 'src-plus']
                    res.srcDirs = ['res', 'res-plus']
                }
                releasePlus.setRoot('build-types/releasePlus')
            }
        }
    }
}

Answer 1

尝试使用下一个结构：

android {

    sourceSets {
        main {
            manifest.srcFile 'AndroidManifest.xml'
        }

        debug {
            manifest.srcFile 'debug/AndroidManifest.xml'
        }

        release {
            manifest.srcFile 'release/AndroidManifest.xml'
        }
    }
}

请注意，gradle会尝试将您的清单合并为一个，但它不像git那样强大，所以很可能您需要复制粘贴整个文件。它适用于2，但应被视为不良做法。您可以从以下答案中了解如何在AndroidManifest中自动执行更改：Replacing a string in AndroidManifest.xml for a buildvariant doesn't work for Gradle Android Plugin Version > 0.5.4

导入的Eclipse项目 - 使用不同AndroidManifest的Gradle buildTypes

1 个答案: