Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Try out compiling with tool as input to task

Relevant bits:

* JavaCompileWithJavaInstallationsIntegrationTest

* JavaCompile#getCompiler

  1. … 10 more files in changeset.
Distributed test

  1. … 90 more files in changeset.
Distributed test

  1. … 91 more files in changeset.
Ignore failing instant execution tests

  1. … 2 more files in changeset.
Reenable tests

  1. … 1 more file in changeset.
Distributed test

  1. … 21 more files in changeset.
Distributed test

  1. … 21 more files in changeset.
Replace LinkedLists with ArrayLists where possible

  1. … 70 more files in changeset.
Fix AbstractSourceIncrementalCompilationIntegrationTest for the configuration cache

by using a gradle property provider in the build under test

Signed-off-by: Paul Merlin <paul@gradle.com>

Fix AbstractCrossTaskIncrementalJavaCompilationIntegrationTest for the configuration cache

by removing usage of the project at execution time in build under test

Signed-off-by: Paul Merlin <paul@gradle.com>

Add explaining `because` to tests failing with the configuration cache

Signed-off-by: Paul Merlin <paul@gradle.com>

  1. … 12 more files in changeset.
Skip more software model tests with the configuration cache

Signed-off-by: Paul Merlin <paul@gradle.com>

  1. … 5 more files in changeset.
Ignore samples

  1. … 16 more files in changeset.
Ignore samples

  1. … 16 more files in changeset.
Rename `o.g.a.i.lambdas.{Lambdas => SerializableLambdas}`

  1. … 6 more files in changeset.
Rename `o.g.a.i.lambdas.{Lambdas => SerializableLambdas}`

  1. … 6 more files in changeset.
Let `CompilerForkUtils` pass serializable lambda to `doNotCacheIf`

Let `CompilerForkUtils` pass serializable lambda to `doNotCacheIf`

Remove @ToBeFixedForInstantExecution from GroovySourceIncrementalCompilationIntegrationTest

Signed-off-by: Paul Merlin <paul@gradle.com>

Merge branch 'master' into bamboo/master/ie/providers/configuration-time

  1. … 2 more files in changeset.
Spike with installations container

  1. … 6 more files in changeset.
Upgrade JUnit version (#12924)

Upgrade JUnit to 4.13, JUnit platform to 5.6.2

  1. … 329 more files in changeset.
Enable symlink tests with VFS retention

  1. … 2 more files in changeset.
Enable symlink tests with VFS retention

  1. … 2 more files in changeset.
Enable symlink tests with VFS retention

  1. … 2 more files in changeset.
Upgrade JUnit

  1. … 328 more files in changeset.
Remove test precondition: FIX_TO_WORK_ON_JAVA9 (#12940)

Gradle clearly works with Java 9 (and later) by now. There should

be nothing left to be fixed. The remaining usages of this annotation

where wrong:

- The test is not testing a feature of Gradle, but of Java or another

tool that only works with java versions < 9

Replaced precondition with: JDK8_OR_EARLIER

(or JDK9_OR_LATER depending on how it is used)

- Test is running older Gradle versions that do not support Java9+

Replaced precondition with: JDK8_OR_EARLIER

- Test itself was using features of Java not available anymore in Java9+

Removed precondition and fixed test to do the test setup differently.

  1. … 10 more files in changeset.
Remove test precondition: FIX_TO_WORK_ON_JAVA9

Gradle clearly works with Java 9 (and later) by now. There should

be nothing left to be fixed. The remaining usages of this annotation

where wrong:

- The test is not testing a feature of Gradle, but of Java or another

tool that only works with java versions < 9

Replaced precondition with: JDK8_OR_EARLIER

(or JDK9_OR_LATER depending on how it is used)

- Test is running older Gradle versions that do not support Java9+

Replaced precondition with: JDK8_OR_EARLIER

- Test itself was using features of Java not available anymore in Java9+

Removed precondition and fixed test to do the test setup differently.

  1. … 10 more files in changeset.
Remove test precondition: FIX_TO_WORK_ON_JAVA9

Gradle clearly works with Java 9 (and later) by now. There should

be nothing left to be fixed. The remaining usages of this annotation

where wrong:

- The test is not testing a feature of Gradle, but of Java or another

tool that only works with java versions < 9

Replaced precondition with: JDK8_OR_EARLIER

(or JDK9_OR_LATER depending on how it is used)

- Test is running older Gradle versions that do not support Java9+

Replaced precondition with: JDK8_OR_EARLIER

- Test itself was using features of Java not available anymore in Java9+

Removed precondition and fixed test to do the test setup differently.

  1. … 10 more files in changeset.
Fix more

  1. … 89 more files in changeset.