dependencyManagement

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Update to latest commons lang 3 release

This is a quick fix: the test should not check the dynamic version.

    • -1
    • +1
    ./customizingResolution/metadataRule/compileClasspathArtifacts.out
    • -1
    • +1
    ./customizingResolution/metadataRule/runtimeClasspathArtifacts.out
Improve error reporting for the Java ecosystem

This commit introduces improved error messages for the Java ecosystem

in case of variant matching errors.

    • -33
    • +33
    ./customizingResolution/metadataRule/failRuntimeClasspathResolve.out
  1. … 26 more files in changeset.
Improve error reporting for the Java ecosystem

This commit introduces improved error messages for the Java ecosystem

in case of variant matching errors.

    • -33
    • +33
    ./customizingResolution/metadataRule/failRuntimeClasspathResolve.out
  1. … 26 more files in changeset.
Improve error reporting for the Java ecosystem

This commit introduces improved error messages for the Java ecosystem

in case of variant matching errors.

    • -33
    • +33
    ./customizingResolution/metadataRule/failRuntimeClasspathResolve.out
  1. … 26 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

    • -1
    • +96
    ./customizingResolution/metadataRule/failRuntimeClasspathResolve.out
  1. … 46 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

    • -1
    • +1
    ./customizingResolution/metadataRule/failRuntimeClasspathResolve.out
  1. … 46 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

    • -1
    • +96
    ./customizingResolution/metadataRule/failRuntimeClasspathResolve.out
  1. … 46 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

    • -1
    • +96
    ./customizingResolution/metadataRule/failRuntimeClasspathResolve.out
  1. … 46 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

    • -1
    • +1
    ./customizingResolution/metadataRule/failRuntimeClasspathResolve.out
  1. … 45 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

    • -1
    • +1
    ./customizingResolution/metadataRule/failRuntimeClasspathResolve.out
  1. … 45 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

    • -1
    • +1
    ./customizingResolution/metadataRule/failRuntimeClasspathResolve.out
  1. … 44 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

    • -1
    • +96
    ./customizingResolution/metadataRule/failRuntimeClasspathResolve.out
  1. … 46 more files in changeset.
Fix spelling mistakes and logical/structural errors in the userguide

Signed-off-by: Lars Kaulen <lars.kaulen@outlook.de>

  1. … 19 more files in changeset.
ivyMetadataRule: fix kotlin dsl example for IvyModuleDescriptor class

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

Update enterprise plugin to latest 3.2 release

    • -1
    • +1
    ./customizingResolution/metadataRule/compileClasspathArtifacts.out
    • -1
    • +1
    ./customizingResolution/metadataRule/runtimeClasspathArtifacts.out
  1. … 5 more files in changeset.
ivyMetadataRule: add comments for filter out of non ivy modules

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

Document the single lock file per project

Issue #11881

  1. … 1 more file in changeset.
Document the single lock file per project

Issue #11881

  1. … 1 more file in changeset.
Document the single lock file per project

Issue #11881

  1. … 1 more file in changeset.
Document the single lock file per project

Issue #11881

  1. … 1 more file in changeset.
Document the single lock file per project

Issue #11881

  1. … 1 more file in changeset.
Use a property for LockMode

This is more inline with modern Gradle APIs and enables the usage of

finalized value instead of doing it internally.

  1. … 8 more files in changeset.
Use a property for LockMode

This is more inline with modern Gradle APIs and enables the usage of

finalized value instead of doing it internally.

  1. … 8 more files in changeset.
Use a property for LockMode

This is more inline with modern Gradle APIs and enables the usage of

finalized value instead of doing it internally.

  1. … 8 more files in changeset.
Use a property for LockMode

This is more inline with modern Gradle APIs and enables the usage of

finalized value instead of doing it internally.

  1. … 8 more files in changeset.
Use a property for LockMode

This is more inline with modern Gradle APIs and enables the usage of

finalized value instead of doing it internally.

  1. … 8 more files in changeset.
ivy-component-metadata-rule sample should check for IvyModuleDescriptor existence to avoid breaking Maven modules

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

Trigger ivy rule in samples

Fix test failures

  1. … 4 more files in changeset.
Update samples to actually execute the component rules