dependencyManagement

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Revert "Revert "Merge branch 'release'""

This reverts commit 67b8bb8f18f854f45a2f5ec52cc9c8a25981e2f2.

This restores the merge attempt from earlier.

    • -0
    • +15
    ./managingTransitiveDependencies/declaringCapabilities/declaring-capabilities.sample.conf
  1. … 63 more files in changeset.
Revert "Merge branch 'release'"

This reverts commit c7fdc455dcb9a8016af0ae9bc8b4c43fde1e2d06, reversing

changes made to 9f70d52b74dbc8c71381781b6c155474031b3cf8.

The changes need a wrapper as there are API changes. Reverting for now.

    • -15
    • +0
    ./managingTransitiveDependencies/declaringCapabilities/declaring-capabilities.sample.conf
  1. … 63 more files in changeset.
Support variant selection in capability conflict resolution (#10973)

A conflict can also occur between two variants of the same component.

This gives access to the variant name in the selection rule and

evicts nodes that represent the not-selected variant.

    • -0
    • +15
    ./managingTransitiveDependencies/declaringCapabilities/declaring-capabilities.sample.conf
    • -0
    • +38
    ./managingTransitiveDependencies/declaringCapabilities/dependencyReportReplaced.out
  1. … 10 more files in changeset.
Support variant selection in capability conflict resolution

A conflict can also occur between two variants of the same component.

This gives access to the variant name in the selection rule and

evicts nodes that represent the not-selected variant.

    • -0
    • +15
    ./managingTransitiveDependencies/declaringCapabilities/declaring-capabilities.sample.conf
  1. … 10 more files in changeset.
Support variant selection in capability conflict resolution

A conflict can also occur between two variants of the same component.

This gives access to the variant name in the selection rule and

evicts nodes that represent the not-selected variant.

    • -0
    • +15
    ./managingTransitiveDependencies/declaringCapabilities/declaring-capabilities.sample.conf
    • -0
    • +38
    ./managingTransitiveDependencies/declaringCapabilities/dependencyReportReplaced.out
  1. … 9 more files in changeset.
Enhance cross project publication sample

Added info on how to setup the configuration to share the same

dependencies.

Enhance cross project publication sample

Added info on how to setup the configuration to share the same

dependencies.

Fix result of capabilities conflict

The documentation still used the old message / format

  1. … 2 more files in changeset.
Fix result of capabilities conflict

The documentation still used the old message / format

  1. … 2 more files in changeset.
Add documentation about `failOnXXX` methods

    • -0
    • +11
    ./managingTransitiveDependencies/resolutionStrategy/resolution-strategy.sample.conf
  1. … 3 more files in changeset.
Add documentation about `failOnXXX` methods

    • -0
    • +11
    ./managingTransitiveDependencies/resolutionStrategy/resolution-strategy.sample.conf
  1. … 3 more files in changeset.
Rewrite section on 'excluding dependencies'

    • -2
    • +6
    ./managingTransitiveDependencies/excludeForConfiguration/exclude-transitive-for-configuration.sample.conf
    • -2
    • +30
    ./managingTransitiveDependencies/excludeForDependency/exclude-transitive-for-dependency.sample.conf
  1. … 18 more files in changeset.
Rewrite section on 'excluding dependencies'

    • -2
    • +6
    ./managingTransitiveDependencies/excludeForConfiguration/exclude-transitive-for-configuration.sample.conf
    • -2
    • +30
    ./managingTransitiveDependencies/excludeForDependency/exclude-transitive-for-dependency.sample.conf
  1. … 18 more files in changeset.
Suppress remaining deprecation warnings

- most are because of the use of the deprecated Maven plugin

- some are because of the deprecated `force` option in dependency management

- +1: Ratpack plugin used "compile" configuration

    • -0
    • +4
    ./managingTransitiveDependencies/forceForDependency/force-per-dependency.sample.conf
  1. … 9 more files in changeset.
Use HTTPS instead of HTTP in samples

  1. … 2 more files in changeset.
Remove obsolete section

This is already covered in the section about rich versions and

strictly now.

  1. … 2 more files in changeset.
Add support for deactivateDependencyLocking to disable locking on configurations

Signed-off-by: Roberto Perez Alcolea <rperezalcolea@netflix.com>

  1. … 8 more files in changeset.
Rewrite section on component metadata rules (#10735)

The section was written when the very first version of rules was

introduced and since then only marginally updated.

This is a complete rewrite of the section focusing on explaining

all the metadata modeling features of Gradle Module Metadata

which can be utilized in rules to enrich existing metadata.

The features are described on using real-world use cases.

Related sections are also updated where applicable.

    • -0
    • +1
    ./customizingResolution/ivyMetadataRule/compileClasspathArtifacts.out
    • -0
    • +25
    ./customizingResolution/ivyMetadataRule/ivyComonentMetadataRule.sample.conf
    • -0
    • +2
    ./customizingResolution/ivyMetadataRule/runtimeClasspathArtifacts.out
  1. … 45 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions() (#10755)

This name change more clearly communicates the semantics of the

feature from a users point of view.

This commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

would have been misleading in the future. To make sure we catch all,

this also updates all variable/method/package names.

    • -0
    • +9
    ./declaringDependencies/strictForSubgraph/dependencies-strict.sample.conf
  1. … 65 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

  1. … 65 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

  1. … 65 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

    • -0
    • +9
    ./declaringDependencies/strictForSubgraph/dependencies-strict.sample.conf
  1. … 65 more files in changeset.
Update documentation on forcing dependencies

Now that `force` is deprecated, we should recommend and

better describe the semantics of "strictly".

  1. … 1 more file in changeset.
Update documentation on forcing dependencies

Now that `force` is deprecated, we should recommend and

better describe the semantics of "strictly".

  1. … 1 more file in changeset.
Use instantiator for DSL objects created through SoftwareComponentFactory

To have a better and consistent DSL experience when using:

component.addVariantsFromConfiguration(...) { ... }

component.withVariantsFromConfiguration(...) { ... }

  1. … 10 more files in changeset.
Use instantiator for DSL objects created through SoftwareComponentFactory

To have a better and consistent DSL experience when using:

component.addVariantsFromConfiguration(...) { ... }

component.withVariantsFromConfiguration(...) { ... }

  1. … 9 more files in changeset.
Rewrite section on component metadata rules

The section was written when the very first version of rules was

introduced and since then only marginally updated.

This is a complete rewrite of the section focusing on explaining

all the metadata modeling features of Gradle Module Metadata

which can be utilized in rules to enrich existing metadata.

The features are described on using real-world use cases.

Related sections are also updated where applicable.

    • -0
    • +25
    ./customizingResolution/ivyMetadataRule/ivyComonentMetadataRule.sample.conf
  1. … 43 more files in changeset.
Updating docs wip

  1. … 5 more files in changeset.
Rewrite section on component metadata rules

The section was written when the very first version of rules was

introduced and since then only marginally updated.

This is a complete rewrite of the section focusing on explaining

all the metadata modeling features of Gradle Module Metadata

which can be utilized in rules to enrich existing metadata.

The features are described on using real-world use cases.

Related sections are also updated where applicable.

    • -0
    • +25
    ./customizingResolution/ivyMetadataRule/ivyComonentMetadataRule.sample.conf
  1. … 43 more files in changeset.
Rewrite of section on component metadata rules

The section was written when the very first version of rules was

introduced and since then only marginally updated.

This is a complete rewrite of the section focusing explaining

all the metadata modeling features of Gradle Module Metadata

which can be utilized in rules to complete existing metadata.

The features are described on using real-world use cases.

Related sections are also updated where applicable.

    • -0
    • +1
    ./customizingResolution/ivyMetadataRule/compileClasspathArtifacts.out
    • -0
    • +25
    ./customizingResolution/ivyMetadataRule/ivyComonentMetadataRule.sample.conf
    • -0
    • +2
    ./customizingResolution/ivyMetadataRule/runtimeClasspathArtifacts.out
  1. … 43 more files in changeset.