Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Make selected variant known to artifact resolving

This will allow us to use different resolving strategies depending

on the variant that carries the artifact(s). We need this to allow

modules with variants from mixed origins. For example, a module

with only pom metadata, which carries additional variants added

by component metadata rules.

  1. … 11 more files in changeset.
Make selected variant known to artifact resolving

This will allow us to use different resolving strategies depending

on the variant that carries the artifact(s). We need this to allow

modules with variants from mixed origins. For example, a module

with only pom metadata, which carries additional variants added

by component metadata rules.

  1. … 11 more files in changeset.
Make selected variant known to artifact resolving

This will allow us to use different resolving strategies depending

on the variant that carries the artifact(s). We need this to allow

modules with variants from mixed origins. For example, a module

with only pom metadata, which carries additional variants added

by component metadata rules.

  1. … 11 more files in changeset.
Make selected variant known to artifact resolving

This will allow us to use different resolving strategies depending

on the variant that carries the artifact(s). We need this to allow

modules with variants from mixed origins. For example, a module

with only pom metadata, which carries additional variants added

by component metadata rules.

  1. … 11 more files in changeset.
Make selected variant known to artifact resolving

This will allow us to use different resolving strategies depending

on the variant that carries the artifact(s). We need this to allow

modules with variants from mixed origins. For example, a module

with only pom metadata, which carries additional variants added

by component metadata rules.

  1. … 11 more files in changeset.
Make selected variant known to artifact resolving

This will allow us to use different resolving strategies depending

on the variant that carries the artifact(s). We need this to allow

modules with variants from mixed origins. For example, a module

with only pom metadata, which carries additional variants added

by component metadata rules.

  1. … 11 more files in changeset.
Make selected variant known to artifact resolving

This will allow us to use different resolving strategies depending

on the variant that carries the artifact(s). We need this to allow

modules with variants from mixed origins. For example, a module

with only pom metadata, which carries additional variants added

by component metadata rules.

  1. … 11 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 31 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 31 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 25 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 25 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 30 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 31 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 31 more files in changeset.
Add support for adding variants and files to component metadata rules

  1. … 28 more files in changeset.
Fix AttributeConfigurationSelector to return the filtered result

  1. … 1 more file in changeset.
Add support for adding variants and files to component metadata rules

  1. … 21 more files in changeset.
Replace some direct instantiation of `FileResolver` instances with a service.

  1. … 24 more files in changeset.
Replace some direct instantiation of `FileResolver` instances with a service.

  1. … 24 more files in changeset.
Replace some direct instantiation of `FileResolver` instances with a service.

  1. … 24 more files in changeset.
Replace some direct instantiation of `FileResolver` instances with a service.

  1. … 24 more files in changeset.
Replace some direct instantiation of `FileResolver` instances with a service.

  1. … 24 more files in changeset.
Merge branch 'master' into feature/JLL/depricate_http_download_dependencies

* master: (724 commits)

Highlight Gradle Module Metadata support as feature of the release

Add note about configurations deprecations

Increase DaemonErrorFeedbackCrossVersionSpec timeout

Recognize contributor

recognize contributor

Publish 5.6-20190819230034+0000

Remove no longer necessary instant execution codecs for `EnumSet` and `EnumMap`

Improve instant execution support for Java serialization

Polish `BeanPropertyReader.kt`

Polish `BeanCodecTest`

Polish `Codec.kt`

Introduce `SerializableWriteObjectCodec`

Polish `ClosureCodec`

Prepare `BindingsBackedCodec` to accept multiple encodings for the same binding

Simplify `BindingsBackedCodec` usage

Polish `BindingsBackedCodec`

Polish `LoadDirectoryTest`

Remove unused `SerializationFixture` class

Use latest Scan plugin 2.4.1-rc-1

Move Play plugins retirement to 7.0 for now

...

  1. … 19 more files in changeset.
Support dependency artifact in GMM

This is a compatibility layer for seamless migration to GMM.

  1. … 13 more files in changeset.
Support dependency artifact in GMM

This is a compatibility layer for seamless migration to GMM.

  1. … 13 more files in changeset.
Support dependency artifact selectors in Gradle Module Metadata

This is a compatibility feature for combining GMM and pure pom/ivy

modules.

  1. … 13 more files in changeset.
Drop tryDelete()

  1. … 3 more files in changeset.
Drop tryDelete()

  1. … 3 more files in changeset.
Move Deleter interface out of impl package

  1. … 41 more files in changeset.
Move Deleter interface out of impl package

  1. … 38 more files in changeset.