Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Spike AbstractTestTask

  1. … 54 more files in changeset.
Fix bndlib release notes

We actually use 3.4.0

    • -4
    • +2
    /subprojects/docs/src/docs/release/notes.md
Fix formatting of release notes related to Play

And removed a TODO

    • -4
    • +14
    /subprojects/docs/src/docs/release/notes.md
Merge branch 'dd/build-ops/project-structure'

Fix child projects in project structure build operation

Fix Javadoc

Check that cached jacoco report is the same

Increase timeout in test

Activate test which is now implemented

During cleanup: kill processes with main class in the default package

Malfunctioning tests may also keep java processes running that do not

have the main class in `org.gradle`, but declare no package at all.

For example:

- ToolingApiIntegrationTest.tooling API does not hold JVM open

Added `@Nullable` to a couple of methods.

Minor optimization to reported logging hotspot

Fixed the Xcode plugin to honor changes that are made to the locations of the output files for Swift and C++ components, for example when the build directory, base name or module are changed from their default values.

Changed the Xcode plugin to query the link task to determine the location of the output binary file for C++ components rather than assuming it will be found at a particular location. Also default to the capitalized project name for the Xcode product and target names for C++ components.

Reuse local variable to avoid re-canonicalizing file

Changed the Xcode plugin to query the link task to determine the location of the output binary file rather than assuming it will be found at a particular location. Also use the Swift module name or C++ project name to determine the product and target names rather than using the name of the output file.

When a `gradlew` script is not found, use the `gradle` script from Gradle home of the Gradle instance that generates the Xcode files rather than using the `gradle` command from the $PATH.

Use DSL convenience instead of `set()` method to set value of some properties in tests.

Added some TODOs.

Fixed some unit tests for changes to `Directory` and `RegularFile`.

Mention DSL convenience for properties of type `PropertyState` in release notes.

    • -1
    • +7
    /subprojects/docs/src/docs/release/notes.md
Revert "Make performance tests stricter"

This lead to too many false positives. We either

need to make our infrastructure deliver more precise

results or apply better statistical analysis.

Exclude misbehaving performance test

Fix RunningPlayApp since this is used when running Play outside of Gradle too

Revert "Revert "Look for the Play started message from Gradle vs Play""

This reverts commit e30c0ec54a32826550641ac9f095856c0ef2e5d2.

Revert "Look for the Play started message from Gradle vs Play"

This reverts commit 7318e374a7232b2c9bca7511eb8e280445217f37.

Look for the Play started message from Gradle vs Play

The Play framework seems to say its listening before the Play application fully starts

which causes a race condition in our integration tests.

Gradle produces a similar message after the Play application has had

time to start, so this should be after the application is ready.

Accept small first use regression

The `FileHasher` is now always initialized early

instead of when the first task with inputs runs.

This is not a problem, because the scenario of

"starting the daemon, but never running a task

with inputs" is unrealistic.

Merge pull request #2716 from gradle/oehme/performance/zip

Make zipTree and tarTree faster

    • -2
    • +6
    /subprojects/docs/src/docs/release/notes.md
Rebaseline all performance tests

  1. … 9 more files in changeset.
Merge pull request #2749 from gradle/oehme/performance/stricter

Make performance tests stricter