Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Deprecate afterEvaluate invocation after a project is evaluated

Calling afterEvaluate once the project is evaluated has no effect (aka

the action is never called). We are converting the silent ignore of the

action into a deprecation warning which will then become an error in

Gradle 7.0.

Run santa tracker Java as well

    • -2
    • +14
    /subprojects/performance/templates.gradle
all reruns

    • -2
    • +14
    /subprojects/performance/templates.gradle
Run santa tracker Java as well

    • -2
    • +14
    /subprojects/performance/templates.gradle
Run santa tracker Java as well

    • -2
    • +14
    /subprojects/performance/templates.gradle
Fix test expectation

Instead of comparing output that contains irrelevant dots, we strip them

before asserting that we have the expected percentage values

Added a method that allows to query the output for a line containing a

given String

Fix test expectation

Instead of comparing output that contains irrelevant dots, we strip them

before asserting that we have the expected percentage values

Added a method that allows to query the output for a line containing a

given String

Fix test expectation

Instead of comparing output that contains irrelevant dots, we strip them

before asserting that we have the expected percentage values

Added a method that allows to query the output for a line containing a

given String

Fix test expectation

Instead of comparing output that contains irrelevant dots, we strip them

before asserting that we have the expected percentage values

Added a method that allows to query the output for a line containing a

given String

Revert "Merge pull request #10795 from gradle/lacasseio/deprecate-methods-on-start-parameter"

This reverts commit 40cb80789fed1f36e5501d9e8ac35fcb290c6b76, reversing

changes made to f6c349254943c709e33dd409729174f5adf9f6ce.

Mention search upward related APIs deprecation

Mention C++ and Swift promotion in release notes

    • -0
    • +5
    /subprojects/docs/src/docs/release/notes.md
Restructure parts about components and artifacts in publishing chapter

- Start with adjusting components from java plugins

(most common and simple use case, can be used to add custom artifacts,

includes updated 'javadoc' sample now)

- Extra section on creating completely new components

- Only one section about artifacts, starting with the warning,

recommending to not mix components and artifacts

Restructure parts about components and artifacts in publishing chapter

- Start with adjusting components from java plugins

(most common and simple use case, can be used to add custom artifacts,

includes updated 'javadoc' sample now)

- Extra section on creating completely new components

- Only one section about artifacts, starting with the warning,

recommending to not mix components and artifacts

Restructure parts about components and artifacts in publishing chapter

- Start with adjusting components from java plugins

(most common and simple use case, can be used to add custom artifacts,

includes updated 'javadoc' sample now)

- Extra section on creating completely new components

- Only one section about artifacts, starting with the warning,

recommending to not mix components and artifacts

Bump max Java version to 13 and experimental Java version to 14

Fix failing test

Looks like different changes caused the distribution to grow.

As we print one dot per MB, this caused a test failure.

This fix will resolve the failure to unblock CI while a better assertion

is created to not have this again in the future

Deprecate BuildListener#buildStarted and Gradle#buildStarted

Registering this callback within an init, settings or build script has

no effect as the build is already started. Those callback are also part

of an older API. Removing it from the public API will prevent further

user confusion.

Deprecate BuildListener#buildStarted and Gradle#buildStarted

Registering this callback within an init, settings or build script has

no effect as the build is already started. Those callback are also part

of an older API. Removing it from the public API will prevent further

user confusion.

Deprecate BuildListener#buildStarted and Gradle#buildStarted

Registering this callback within an init, settings or build script has

no effect as the build is already started. Those callback are also part

of an older API. Removing it from the public API will prevent further

user confusion.

Deprecate BuildListener#buildStarted and Gradle#buildStarted

Registering this callback within an init, settings or build script has

no effect as the build is already started. Those callback are also part

of an older API. Removing it from the public API will prevent further

user confusion.

Deprecate BuildListener#buildStarted and Gradle#buildStarted

Registering this callback within an init, settings or build script has

no effect as the build is already started. Those callback are also part

of an older API. Removing it from the public API will prevent further

user confusion.

Deprecate BuildListener#buildStarted and Gradle#buildStarted

Registering this callback within an init, settings or build script has

no effect as the build is already started. Those callback are also part

of an older API. Removing it from the public API will prevent further

user confusion.

Recognize contribution

    • -0
    • +1
    /subprojects/docs/src/docs/release/notes.md
Rebaseline NativeCleanBuildPerformanceTest

See https://github.com/gradle/gradle-private/issues/2714

Add Javadoc/sources publishing changes to notes and upgrading guide

    • -0
    • +15
    /subprojects/docs/src/docs/release/notes.md
Add Javadoc/sources publishing changes to notes and upgrading guide

    • -0
    • +15
    /subprojects/docs/src/docs/release/notes.md
Add Javadoc/sources publishing changes to notes and upgrading guide

    • -0
    • +15
    /subprojects/docs/src/docs/release/notes.md
Add cross build test for santa tracker