Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'release'

Use fixed version to check for binary compatibility

Make tests using play.test.WithBrowser wait for port 19001 to be free

This should fix flakiness of

'UserGuidePlaySamplesIntegrationTest.compiler sample is buildable'

Do not attempt to execute 'jstack' if it does not exist

IBM VMs do not provide it.

Expect deprecation warning for Gradle versions 1.1 - 1.12

Copy remote cache artifacts into local cache 2

Fixes some issues and improves test coverage

Ensure that jre is valid for different jvm

Ensure that jre is valid for different jvm

Disable tests that won't work on Java 9

Disable tests that won't work on Java 9

Ignore tests when run in parallel as they won't behave the same

Ignore tests when run in parallel as they won't behave the same

Requires String interpolation to work properly

Polish FindBugs progress option

    • -0
    • +1
    /subprojects/docs/src/docs/release/notes.md
Merge pull request #2425 from gradle/gh/worker-api/set-executable

Worker daemons respect all java fork options settings

Add an option to FindBugs to disable analysis progress (#2181)

This fixes https://github.com/gradle/gradle/issues/1646,

https://github.com/gradle/gradle/issues/1307,

https://github.com/gradle/gradle/issues/1756

It has been reported that FindBugs plugin will always print analysis

progress to standard output no matter what the configuration is. It is

because '-progress' command line option is always activated when

staring FindBugs in FindBugsSpecBuilder. This commit add an option to

FindBugs plugin named 'showProgress' to control it. If set to false,

'-progress' will not be passed to FindBugs.

    • -1
    • +5
    /subprojects/docs/src/docs/dsl/org.gradle.api.plugins.quality.FindBugsExtension.xml
Add missing exception message

More robust approach to system-specific path

Only accept binary breaking changes to Incubating methods

Store task state even if task has failed (#2383)

Previously when a failing task created new files, those files would be recognized as overlapping outputs from some unknown source. Overlapping outputs would then cause task output caching to be disabled for the task.

We now persist the task's state even after a failed execution. But in the failure case we only persist the snapshots if there was a change to the outputs. When we do this, we also record that the execution failed. However, if the failing task didn't change its outputs, there is no need to persist its state. This will allow the task to run in incremental mode the next time it's executed.

For tasks that do modify their outputs incremental execution was always disabled the next time they were executed, and this change preserves that behavior.

  1. … 21 more files in changeset.
Make it possible to accept incubating regressions

Method needs to be public

Quick fix for fixing binary breakage test

#2399

Don't render test worker info in console

    • -4
    • +4
    /subprojects/docs/src/docs/release/notes.md
Make `ScalaCompile` and `ScalaDoc` cacheable (#2399)

This adds test coverage with respect to caching and incremental builds for `ScalaCompile` and `ScalaDoc` and makes both tasks cacheable.

Issue: #1956

Based on PR: #1958

    • -0
    • +11
    /subprojects/docs/src/docs/release/notes.md
  1. … 9 more files in changeset.
Bump version number {0.10.3 => 0.11.0-SNAPSHOT}

Merge pull request #419 from gradle/develop

0.10.3

Upgrade gradle-kotlin-dsl {0.10.2 => 0.10.3}

https://github.com/gradle/kotlin-dsl/releases/tag/v0.10.3

Make CodeNarc happy

Add missing `@Incubating`