JavaCompileJavaVersionIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Change more tests.

    • -2
    • +2
    ./JavaCompileJavaVersionIntegrationTest.groovy
  1. … 40 more files in changeset.
Change more tests.

    • -4
    • +4
    ./JavaCompileJavaVersionIntegrationTest.groovy
  1. … 13 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -6
    • +6
    ./JavaCompileJavaVersionIntegrationTest.groovy
  1. … 98 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -6
    • +6
    ./JavaCompileJavaVersionIntegrationTest.groovy
  1. … 98 more files in changeset.
Changed a bunch of integration tests to use the various task assertion methods instead of directly querying the `executedTasks` and `skippedTasks` collections. These methods can give better diagnostics when the assertion fails, and can perform additional checks.

    • -6
    • +6
    ./JavaCompileJavaVersionIntegrationTest.groovy
  1. … 98 more files in changeset.
Raise minimum build JVM version to Java 8

    • -11
    • +11
    ./JavaCompileJavaVersionIntegrationTest.groovy
  1. … 30 more files in changeset.
Use daemon by default when forking from embedded executor

The Play! integration tests always fork a new process

so that they can cancel it. The embedded executor was

using no-daemon mode when asked for a forking handle.

This is now changed to use a daemon instead, greatly

speeding up the Play! integreation tests in embedded

mode.

I stumbled over a bug in our module registry that made

it impossible to run anything in IntelliJ in embedded

mode that used a type from the "plugins" project.

I suspect that some "requireDistribution" usages might

be just because of this bug. We should definitely check that.

There was also some inconsistency in how the embedded executor

handled jvm args and environment variables when it forked a

process. This went unnoticed because it wasn't using the daemon

and the arguments it was missing were to work around issues in

daemon mode. This is now fixed by extending the daemon executor.

    • -0
    • +10
    ./JavaCompileJavaVersionIntegrationTest.groovy
  1. … 9 more files in changeset.
Fix test

Now we track the version, not the Java version.

+review REVIEW-6467

    • -2
    • +2
    ./JavaCompileJavaVersionIntegrationTest.groovy
Track only the major version of the Java toolchain

+review REVIEW-6467

    • -0
    • +118
    ./JavaCompileJavaVersionIntegrationTest.groovy
  1. … 5 more files in changeset.