Question

我有一个gradle（1.8）项目，有2个A和B类，其中B导入A.两个文件都在/foo/bar/包下（myProjectFolder / test / foo / bar文件夹）。

A.groovy class

package foo.bar

import org.junit.Test;

public class ATest{ 
    @Test
    public void run() {
        System.out.println("CLASS A");
    }
}

B.groovy class

package foo.bar

import org.junit.Test;

public class BTest{
    @Test
    public void run() {
        ATest a = new ATest();
        a.run();
        System.out.println("CLASS B");
    }
}

的build.gradle

apply plugin: "groovy"
apply plugin: "java"

repositories {
        mavenCentral()
}

dependencies {
        groovy group: "org.codehaus.groovy", name:"groovy-all", version: "1.8.6"
        testCompile "junit:junit:4.10"
}

test {
        testLogging.showStandardStreams = true
}

sourceSets {
        test { groovy {
                srcDir 'test/foo/bar'
        } }
}

buildscript {
        repositories { mavenCentral() }
}

configurations{
    addToClassLoader
}

dependencies {
    addToClassLoader "junit:junit:4.10"
}

URLClassLoader loader = GroovyObject.class.classLoader
configurations.addToClassLoader.each {File file ->

loader.addURL(file.toURL())
}

task runA << {
    new GroovyShell().run(file('test/foo/bar/ATest.groovy'));
}

task runB << {
    new GroovyShell().run(file('test/foo/bar/BTest.groovy'));
}

gradle clean -Dtest.single=A test

的输出控制台

[root@vm1]# gradle clean -Dtest.single=A test
The groovy configuration has been deprecated and is scheduled to be removed in Gradle 2.0. Typically, usages of 'groovy' can simply be replaced with 'compile'. In some cases, it may be necessary to additionally configure the 'groovyClasspath' property of GroovyCompile and Groovydoc tasks.
:clean
:compileJava UP-TO-DATE
:compileGroovy UP-TO-DATE
:processResources
:classes
:compileTestJava UP-TO-DATE
:compileTestGroovy
:processTestResources UP-TO-DATE
:testClasses
:test
foo.bar.ATest > run STANDARD_OUT
    CLASS A
BUILD SUCCESSFUL
Total time: 13.205 secs

gradle clean -Dtest.single=B test

的输出控制台

[root@vm1]# gradle clean -Dtest.single=B test
The groovy configuration has been deprecated and is scheduled to be removed in Gradle 2.0. Typically, usages of 'groovy' can simply be replaced with 'compile'. In some cases, it may be necessary to additionally configure the 'groovyClasspath' property of GroovyCompile and Groovydoc tasks.
:clean
:compileJava UP-TO-DATE
:compileGroovy UP-TO-DATE
:processResources
:classes
:compileTestJava UP-TO-DATE
:compileTestGroovy
:processTestResources UP-TO-DATE
:testClasses
:test
foo.bar.BTest > run STANDARD_OUT
    CLASS A
    CLASS B
BUILD SUCCESSFUL
Total time: 12.218 secs

gradle -q runA -i

的输出控制台

[root@vm1]# gradle -q runA -i
Starting Build
Settings evaluated using empty settings script.
Projects loaded. Root project using build file '/opt/myProject/build.gradle'.
Included projects: [root project 'myProject']
Evaluating root project 'myProject' using build file '/opt/myProject/build.gradle'.
Starting file lock listener thread.
The groovy configuration has been deprecated and is scheduled to be removed in Gradle 2.0. Typically, usages of 'groovy' can simply be replaced with 'compile'. In some cases, it may be necessary to additionally configure the 'groovyClasspath' property of GroovyCompile and Groovydoc tasks.
All projects evaluated.
Selected primary task 'runA'
Tasks to be executed: [task ':runA']
:runA (Thread[main,5,main]) started.
:runA
Executing task ':runA' (up-to-date check took 0.001 secs) due to:
  Task has not declared any outputs.
CLASS A
JUnit 4 Runner, Tests: 1, Failures: 0, Time: 63
:runA (Thread[main,5,main]) completed. Took 0.739 secs.
BUILD SUCCESSFUL
Total time: 7.826 secs

gradle -q runB -i 的输出控制台＆lt; - 此执行失败，我不知道原因。

[root@vm1]# gradle -q runB -i
Starting Build
Settings evaluated using empty settings script.
Projects loaded. Root project using build file '/opt/myProject/build.gradle'.
Included projects: [root project 'myProject']
Evaluating root project 'myProject' using build file '/opt/myProject/build.gradle'.
Starting file lock listener thread.
The groovy configuration has been deprecated and is scheduled to be removed in Gradle 2.0. Typically, usages of 'groovy' can simply be replaced with 'compile'. In some cases, it may be necessary to additionally configure the 'groovyClasspath' property of GroovyCompile and Groovydoc tasks.
All projects evaluated.
Selected primary task 'runB'
Tasks to be executed: [task ':runB']
:runB (Thread[main,5,main]) started.
:runB
Executing task ':runB' (up-to-date check took 0.001 secs) due to:
  Task has not declared any outputs.
:runB FAILED
:runB (Thread[main,5,main]) completed. Took 0.237 secs.

FAILURE: Build failed with an exception.
* Where:
Build file '/opt/myProject/build.gradle' line: 46
* What went wrong:
Execution failed for task ':runB'.
> startup failed:
  /opt/myProject/test/foo/bar/BTest.groovy: 8: unable to resolve class ATest
   @ line 8, column 9.
                ATest a = new ATest();
             ^
  /opt/myProject/test/foo/bar/BTest.groovy: 8: unable to resolve class ATest
   @ line 8, column 13.
                ATest a = new ATest();
                 ^
  2 errors
* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output.
BUILD FAILED
Total time: 7.872 secs

那么，我错过了什么来正确运行任务runB？

Answer 1

注意：问题的前提是基于一个真正非正统的用例，应该予以纠正。也就是说，我可以解释所观察到的行为。

当命令行指定test任务时，~/build/classes/test将添加到类路径中。在运行runB任务的情况下，它不是。因此BTest.groovy无法找到ATest。

要更正它（仅作为插图，不作为真实代码的建议），请考虑：

// don't do this in a real project!
task runB(dependsOn: 'compileTestGroovy') << {
    def testDirURL = new File("${projectDir}/build/classes/test").toURL()
    loader.addURL(testDirURL)
    new GroovyShell(loader).run(file('test/foo/bar/BTest.groovy'))
}

现在，runB要求编译Groovy测试代码，然后手动（！？）将其添加到GroovyShell使用的类加载器中。

Gradle在运行任务时不导入groovy类

1 个答案: