Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Compute the name of PublishArtifactLocalArtifactMetadata lazily

In case where the publish artifact is of type 'LazyPublishArtifact',

this broke the laziness.

Consolidate type validation

Use ValidateContext with a few standard implementations instead of the many different interfaces and implementations we used to collect valdiation problems before. This fixes issues with types being displayed inconsistently.

The implementation is not fully correct yet: we now fail to display the correct type for problems that are bound to a type instead of a property.

  1. … 33 more files in changeset.
Use a default method to reduce number of empty implementations

Steer users away from applying java directly

Updates to the documentation to highlight better the interest of the

`java-library` plugin.

Fixes #7558

Steer users away from applying java directly

Updates to the documentation to highlight better the interest of the

`java-library` plugin.

Fixes #7558

Cleanup worker api samples

Add `@Deprecated` to generated configuration accessors

Add `@Deprecated` to generated configuration accessors

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.

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.

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.

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.

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.

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