Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix tests

Upgrade commons-lang{->3} replacing packages

  1. … 175 more files in changeset.
Change more tests.

  1. … 40 more files in changeset.
Change more tests.

  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.

  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.

  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.

  1. … 98 more files in changeset.
Let tests use 'implementation' and 'testImplementation' configurations

As replacement for 'compile' and 'testCompile'.

  1. … 26 more files in changeset.
Let tests use 'implementation' and 'testImplementation' configurations

As replacement for 'compile' and 'testCompile'.

  1. … 26 more files in changeset.
Let tests use 'implementation' and 'testImplementation' configurations

As replacement for 'compile' and 'testCompile'.

  1. … 26 more files in changeset.
Let tests use 'implementation' and 'testImplementation' configurations

As replacement for 'compile' and 'testCompile'.

  1. … 26 more files in changeset.
Do not use snapshot Groovy versions in tests

When we depend on a SNAPSHOT version of Groovy, we shouldn't run tests that need to download Groovy versions with that SNAPSHOT version. This is to prevent us from bumping into problems with how Groovy snapshots are published.

  1. … 3 more files in changeset.
Upgrade to Groovy 2.5.3-SNAPSHOT (#6903)

This is a temporary measure until Groovy 2.5.3 GA comes out to fix Java 11 incompatibilities.

  1. … 8 more files in changeset.
Upgrade to Groovy 2.5.3-SNAPSHOT (#6903)

This is a temporary measure until Groovy 2.5.3 GA comes out to fix Java 11 incompatibilities.

  1. … 8 more files in changeset.
Raise minimum build JVM version to Java 8

  1. … 30 more files in changeset.
Clean destination directory when running Groovydoc/Javadoc

Both tasks should clean their destination dir to avoid leftover stale

output files.

Issue #6168

  1. … 4 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.

  1. … 9 more files in changeset.
Convert existing relocation tests to use new one (#3782)

  1. … 9 more files in changeset.
On CI redirect maven central queries to local repo for integration tests

  1. … 107 more files in changeset.
Rename groovyCompilerJvmJavaVersion

The new name is still not very understandable, but so is our

Groovy/Java compiler infrastructure.

+review REVIEW-6533

  1. … 1 more file in changeset.
Track the Java toolchain used by the Groovy compiler

+review REVIEW-6533

  1. … 5 more files in changeset.
Address review feedback

- Add comment why we need to track the other Java version

- Remove brittle assert about `--info` logging

- Make new property for Java version tracking private

+review REVIEW-6531

  1. … 3 more files in changeset.
Track Groovy compiler JVM version

+review REVIEW-6531

    • -0
    • +108
    ./org/gradle/language/groovy/GroovyCompileJavaVersionTrackingIntegrationTest.groovy
  1. … 1 more file in changeset.
Fix Groovydoc tests with older version of Groovy

  1. … 1 more file in changeset.
Use common source for tested Groovy versions

+review REVIEW-6505

  1. … 3 more files in changeset.
Mark all the places Groovy needs to be upgraded

+review REVIEW-6505

  1. … 3 more files in changeset.
Upgrade to Groovy 2.4.11

We still refer to Groovy 2.4.10 in several places in documentation and in tests, but that should be okay: those samples and tests don’t need to exercise the current latest version of Groovy.

+review REVIEW-6505

  1. … 2 more files in changeset.
Remove dependency between integTest and test sources

    • -0
    • +23
    ./org/gradle/testing/fixture/GroovydocCoverage.groovy
  1. … 10 more files in changeset.
Accept any kind of Groovydoc output in test

Different versions of Groovy produce different outputs, but they each produce something.

+review REVIEW-6468

Fix test for GroovyDoc output being retained