Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Make it possible to use an ecosystem describer in more cases

Before this commit the describer would only be used if the same set of attributes

was found. This means that if the consumer added, or removed, one attribute, we

would lose the benefit of better user error messages. With this change, we try

to find the _best matching_ describer, if any.

  1. … 6 more files in changeset.
Make it possible to use an ecosystem describer in more cases

Before this commit the describer would only be used if the same set of attributes

was found. This means that if the consumer added, or removed, one attribute, we

would lose the benefit of better user error messages. With this change, we try

to find the _best matching_ describer, if any.

  1. … 6 more files in changeset.
Make it possible to use an ecosystem describer in more cases

Before this commit the describer would only be used if the same set of attributes

was found. This means that if the consumer added, or removed, one attribute, we

would lose the benefit of better user error messages. With this change, we try

to find the _best matching_ describer, if any.

  1. … 6 more files in changeset.
Make it possible to use an ecosystem describer in more cases

Before this commit the describer would only be used if the same set of attributes

was found. This means that if the consumer added, or removed, one attribute, we

would lose the benefit of better user error messages. With this change, we try

to find the _best matching_ describer, if any.

  1. … 5 more files in changeset.
Faster updates on Linux as well

Faster updates on Linux as well

Faster updates on Linux as well

Mention contributor in release notes

    • -1
    • +2
    /subprojects/docs/src/docs/release/notes.md
Merge pull request #12597 from LarsKaulen/documentation-tasks-with-type

Add examples for tasks.withType method to userguide

Mention contributor in release notes

    • -1
    • +2
    /subprojects/docs/src/docs/release/notes.md
Merge pull request #12464 from davidburstrom/master-task-configuration-avoidance-for-wrapper

Use task configuration avoidance in the Wrapper docs

Merge remote-tracking branch 'upstream/master' into documentation-tasks-with-type

Merge remote-tracking branch 'upstream/master' into master-task-configuration-avoidance-for-wrapper

docs: Explain how to update the wrapper JAR itself

This requires to run the wrapper task twice. Also see the related

discussion at [1].

[1] https://discuss.gradle.org/t/gradle-wrapper-jar-not-updated-from-6-0-1-to-6-3/35455

Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>

docs: Slightly improve the wording for updating the wrapper

Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>

Fix for changes.

Fix for changes.

Always prefer Java version configured in release over target/source

This is needed for backwards compatibility with the tooling API

and plugins that rely on the old API to get the Java version

of a project/task.

Always prefer Java version configured in release over target/source

This is needed for backwards compatibility with the tooling API

and plugins that rely on the old API to get the Java version

of a project/task.

Always prefer Java version configured in release over target/source

This is needed for backwards compatibility with the tooling API

and plugins that rely on the old API to get the Java version

of a project/task.

Always prefer Java version configured in release over target/source

This is needed for backwards compatibility with the tooling API

and plugins that rely on the old API to get the Java version

of a project/task.

Always prefer Java version configured in release over target/source

This is needed for backwards compatibility with the tooling API

and plugins that rely on the old API to get the Java version

of a project/task.

Always prefer Java version configured in release over target/source

This is needed for backwards compatibility with the tooling API

and plugins that rely on the old API to get the Java version

of a project/task.

Use plain task dependencies

Use released version of enterprise plugin

Serialize the result of `Provider.flatMap()` to the instant execution cache when the value to be mapped is produced by a task.

Serialize the result of `Provider.flatMap()` to the instant execution cache when the value to be mapped is produced by a task.

Serialize the result of `Provider.flatMap()` to the instant execution cache when the value to be mapped is produced by a task.

Serialize the result of `Provider.flatMap()` to the instant execution cache when the value to be mapped is produced by a task.

Serialize the result of `Provider.flatMap()` to the instant execution cache when the value to be mapped is produced by a task.