Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[WiP] Explicitly declare different Gradle distributions for testing

  1. … 253 more files in changeset.
[WiP] Explicitly declare different Gradle distributions for testing

  1. … 248 more files in changeset.
[WiP] Explicitly declare different Gradle distributions for testing

  1. … 252 more files in changeset.
[WiP] Explicitly declare different Gradle distributions for testing

  1. … 237 more files in changeset.
[WiP] Explicitly declare different Gradle distributions for testing

  1. … 253 more files in changeset.
Test fixes for strictness.

  1. … 15 more files in changeset.
Test fixes for strictness.

  1. … 15 more files in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

  1. … 81 more files in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

  1. … 81 more files in changeset.
Change `AbstractIntegrationSpec` to fail when a test runs a build that fails with more than one exception and does not verify the number of exceptions in the failure using `assertHasFailures()`.

This is to avoid additional exceptions unintentionally being introduced, for example when a failure starts being thrown because of configuration cache problems alongside the expected failure.

  1. … 81 more files in changeset.
Bump default PMD version to 6.23.0 (#12956)

This also fixes the multi-version PMD test setup:

The tests where not configured correctly for running older PMD versions

that do not support incremental analysis.

Also, tests changed the source compatibility for ALL PMD versions to 7,

although newer versions support current Java versions.

  1. … 2 more files in changeset.
Bump default PMD version to 6.23.0

This also fixes the multi-version PMD test setup:

The tests where not configured correctly for running older PMD versions

that do not support incremental analysis.

Also, tests changed the source compatibility for ALL PMD versions to 7,

although newer versions support current Java versions.

  1. … 2 more files in changeset.
Bump default PMD version to 6.23.0

This also fixes the multi-version PMD test setup:

The tests where not configured correctly for running older PMD versions

that do not support incremental analysis.

Also, tests changed the source compatibility for ALL PMD versions to 7,

although newer versions support current Java versions.

  1. … 2 more files in changeset.
Bump default PMD version to 6.23.0

This also fixes the multi-version PMD test setup:

The tests where not configured correctly for running older PMD versions

that do not support incremental analysis.

Also, tests changed the source compatibility for ALL PMD versions to 7,

although newer versions support current Java versions.

  1. … 2 more files in changeset.
Bump default PMD version to 6.23.0

This also fixes the multi-version PMD test setup:

The tests where not configured correctly for running older PMD versions

that do not support incremental analysis.

Also, tests changed the source compatibility for ALL PMD versions to 7,

although newer versions support current Java versions.

  1. … 2 more files in changeset.
Bump default PMD version to 6.23.0

This also fixes the multi-version PMD test setup:

The tests where not configured correctly for running older PMD versions

that do not support incremental analysis.

Also, tests changed the source compatibility for ALL PMD versions to 7,

although newer versions support current Java versions.

  1. … 2 more files in changeset.
Bump default PMD version to 6.23.0

This also fixes the multi-version PMD test setup:

The tests where not configured correctly for running older PMD versions

that do not support incremental analysis.

Also, tests changed the source compatibility for ALL PMD versions to 7,

although newer versions support current Java versions.

  1. … 2 more files in changeset.
Bump default PMD version to 6.23.0

This also fixes the multi-version PMD test setup:

The tests where not configured correctly for running older PMD versions

that do not support incremental analysis.

Also, tests changed the source compatibility for ALL PMD versions to 7,

although newer versions support current Java versions.

  1. … 2 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. … 9 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. … 9 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. … 9 more files in changeset.
Improve error message when PMD incremental analysis is enabled on older version of PMD

Exclude test for instant execution for now

Fix integration test

Enable PMD incrementalAnalysis by default

* Enable by default

* Remove `@Incubating` from APIs

* Add release notes

Enable PMD incrementalAnalysis by default

* Enable by default

* Remove `@Incubating` from APIs

* Add release notes

Do not use ConventionMapping with Property types

Remove always-true JDK8_OR_LATER test precondition

  1. … 40 more files in changeset.
Add snapshots repository in CodeNarc tests

  1. … 1 more file in changeset.
Update CodeNarc coverage range for JDK14