我正在尝试创建一个 Gradle 构建脚本来构建 Java .jar文件处于“发布”或“调试”模式，并且无法参数化脚本。

问题是:使用 Java 插件在 Gradle 脚本中执行此操作的惯用方法是什么？
(或者，如果没有惯用的方法，那么实际有效的hacky解决方案是什么？)

我不介意参数化的方法，只要命令行和 IDE 调用可以轻松地在两个输出选项之间进行选择。 jar 文件将用作其他项目中的库，例如一个 Android 应用程序和一个 JavaFX 应用程序，所以我希望参数化方法可以从他们自己的 Gradle 脚本中调用/依赖。

理想情况下，我想“模拟”Android gradle 插件具有每个任务的调试/发布版本的能力，即

$ ./gradlew build    
$ ./gradlew assembleRelease
$ ./gradlew checkDebug

group 'TestGradleProjectGroup'
apply plugin: 'java'
sourceCompatibility = 1.8

version '1.0-release'
compileJava {
    options.debug = false
}

repositories {
    mavenCentral()
}

dependencies {
    testCompile group: 'junit', name: 'junit', version: '4.11'
}

$ ls TestGradleModule/build/libs/
TestGradleModule-1.0-release.jar

version '1.0-release'
compileJava {
    options.debug = false
}

task buildRelease(type: GradleBuild, dependsOn: build) {
    project.version = '1.0-release'
    compileJava {
        options.debug = false
    }
}

task buildDebug(type: GradleBuild, dependsOn: build) {
    project.version = '1.0-debug'
    compileJava {
        options.debug = true
    }
}

version '1.0-release'
compileJava {
    options.debug = false
}

task buildRelease(type: GradleBuild, dependsOn: build) {
    doLast {
        project.version = '1.0-release'
        compileJava {
            options.debug = false

        }
    }
}

task buildDebug(type: GradleBuild, dependsOn: build) {
    doLast {
        project.version = '1.0-debug'
        compileJava {
            options.debug = true
        }
    }
}

group 'TestGradleProjectGroup'
apply plugin: 'java'
sourceCompatibility = 1.8

configurations {
    debug
    release
}

version '1.0-release'
compileJava {
    options.debug = false
}

repositories {
    mavenCentral()
}

dependencies {
    testCompile group: 'junit', name: 'junit', version: '4.11'
}

gradle.taskGraph.whenReady { taskGraph ->

    taskGraph.allTasks.each { taskIter ->

        println("iterating" + taskIter)

        def releaseTask = project.task(taskIter.name + "Release")
        def debugTask = project.task(taskIter.name + "Debug")

        taskIter.dependsOn += [releaseTask, debugTask].toSet()
        println("new taskIter.dependsOn:" + taskIter.dependsOn)

        /*
            set debug mode here,
            copy over effects of task to debug/release
            disable effects of task
        */
    }
}

最佳答案

经过几个小时的搜索......

“构建脚本基础”的“通过 DAG 配置”部分 Gradle教程描述了一种方法，即

https://docs.gradle.org/current/userguide/tutorial_using_tasks.html#configure-by-dag

引自教程

"Gradle has a configuration phase and an execution phase. After the configuration phase, Gradle knows all tasks that should be executed. Gradle offers you a hook to make use of this information. A use-case for this would be to check if the release task is among the tasks to be executed. Depending on this, you can assign different values to some variables."

gradle.taskGraph.whenReady { taskGraph ->
    if (taskGraph.hasTask(buildRelease)) {
        compileJava.options.debug = false
        project.version = '1.0-release'
    } else if (taskGraph.hasTask(buildDebug)) {
        compileJava.options.debug = true
        project.version = '1.0-debug'
    }
}

task buildRelease(type: GradleBuild, dependsOn: build) {
}

task buildDebug(type: GradleBuild, dependsOn: build) {
}

关于java - 用于构建 'debug' 和 'release' JAR 文件的惯用 Gradle 脚本，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/47390481/