Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Make query methods for deprecation state of core configurations public

This is to allow plugin authors to make use of this information.

The methods to actually deprecate configurations stay internal,

as they are bound to the deprecation mechanism of Gradle core.

And thus they may only be used for configurations of Gradle's core

plugins.

  1. … 12 more files in changeset.
Make query methods for deprecation state of core configurations public

This is to allow plugin authors to make use of this information.

The methods to actually deprecate configurations stay internal,

as they are bound to the deprecation mechanism of Gradle core.

And thus they may only be used for configurations of Gradle's core

plugins.

  1. … 12 more files in changeset.
Fix missing argument in test

Fix missing argument in test

Exclude deprecated configurations from reports

  1. … 7 more files in changeset.
Exclude deprecated configurations from reports

  1. … 7 more files in changeset.
Exclude deprecated configurations from reports

  1. … 7 more files in changeset.
Exclude deprecated configurations from reports

  1. … 7 more files in changeset.
WIP - adjustments + handle annotation processor configurations

  1. … 22 more files in changeset.
WIP - adjustments + handle annotation processor configurations

  1. … 24 more files in changeset.
WIP - adjustments + handle annotation processor configruations

  1. … 22 more files in changeset.
Replace 'Matchers' with 'CoreMatchers'

So we do not require 'org.hamcrest:hamcrest-library' as additional

dependency anymore. Which was only available for most of the tests

because it leaked onto the test compile classpath.

  1. … 162 more files in changeset.
Remove synthetic accessors for internal private symbol references

  1. … 902 more files in changeset.
Remove synthetic accessors for internal private symbol references

  1. … 902 more files in changeset.
Remove synthetic accessors for internal private symbol references

  1. … 890 more files in changeset.
Remove synthetic accessors for internal private symbol references

  1. … 897 more files in changeset.
Remove synthetic accessors for internal private symbol references

  1. … 902 more files in changeset.
Remove synthetic accessors for internal private symbol references

  1. … 902 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 286 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 283 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 286 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 284 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 285 more files in changeset.
Use 'implementation' dependencies everywhere

  1. … 285 more files in changeset.
Initial support for optional features

This commit introduces initial support for optional features, by

implementing a way for a dependency declaration (currently *only* in

the DSL) to request variants of the target component that provide one

or more capabilities.

Previously to this change, selection was (simplified) done like this:

1. find the target component

2. select the variant of the target component which matches the requested

attributes

Now, selection introduces another step:

1. find the target component

2. filter variants by eliminating those which do not provide the requested

capabilities

3. select the variant in this list which matches the requested attributes

Several changes had to be implemented:

First, component metadata rules calling `addCapability` will now return

a component which capabilities _include_ the default capability.

Second, attribute filtering is done in a secondary step, which means that

if there are no variant matching the requested capabilities, we will immediately

fail.

  1. … 58 more files in changeset.
Spelling (#8199)

Fix several spelling issues.

  1. … 36 more files in changeset.
Support depending on multiple variants of the same component

This commit changes the resolution engine so that it is possible

to resolve multiple variants of the same component when using

variant-aware dependency management.

Before, in order to have 2 dependencies on the same component

but using different variants, one had to use explicit configuration

dependencies. Now, with this change, it is possible to have

two dependencies on the same component, but with different attributes.

Those components would resolve to different variants.

Special treatment is applied when attributes are declared on constraints:

in this case, we _merge_ the constraint attributes, and make sure that

the edge is computed using the merged attributes. Should they be

incompatible, the build would fail as before.

  1. … 29 more files in changeset.
spelling: removing

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

spelling: dependency

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

Signed-off-by: Bo Zhang <bo@gradle.com>

  1. … 2 more files in changeset.
Add option to display tasks from a specific group only

Signed-off-by: Alex Saveau <saveau.alexandre@gmail.com>

  1. … 2 more files in changeset.