DependencyInsightOutputNormalizer.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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).

    • -0
    • +1
    ./DependencyInsightOutputNormalizer.groovy
  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).

    • -0
    • +1
    ./DependencyInsightOutputNormalizer.groovy
  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).

    • -0
    • +1
    ./DependencyInsightOutputNormalizer.groovy
  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).

    • -0
    • +1
    ./DependencyInsightOutputNormalizer.groovy
  1. … 46 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
    ./DependencyInsightOutputNormalizer.groovy
  1. … 59 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
    • +1
    ./DependencyInsightOutputNormalizer.groovy
  1. … 59 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
    • +1
    ./DependencyInsightOutputNormalizer.groovy
  1. … 59 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
    • +1
    ./DependencyInsightOutputNormalizer.groovy
  1. … 59 more files in changeset.
To avoid confusion, remove mention of "platform" from "target Java platform"

We already have the "Java Platform" plugin which is something quite

different from the concept we want to express when using "target java platform".

This is more often known as the "JVM version", or "target Java version". We

use "JVM" because this is not specific to Java.

    • -1
    • +1
    ./DependencyInsightOutputNormalizer.groovy
  1. … 25 more files in changeset.
Fix userguide sample output

    • -0
    • +30
    ./DependencyInsightOutputNormalizer.groovy
  1. … 7 more files in changeset.