Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Split up `GradleModuleMetadataWriter` into multiple files

Under the new `o.g.a.publish.internal.metadata` package.

    • -0
    • +30
    ./org/gradle/api/publish/internal/metadata/ComponentData.java
    • -0
    • +93
    ./org/gradle/api/publish/internal/metadata/JsonWriterScope.java
  1. … 2 more files in changeset.
Simplify `GradleModuleMetadataWriter`

By introducing the `ModuleMetadataJsonWriter` method object and hiding the

usages of `JsonWriter` behind the `JsonWriterScope` utility class.

Simplify `GradleModuleMetadataWriter`

By introducing the `ModuleMetadataJsonWriter` method object and hiding the

usages of `JsonWriter` behind the `JsonWriterScope` utility class.

Polish `GenerateModuleMetadata`

- Format document

- Extract `publication()` accessor

- Reorder `generateTo` parameters to improve prose

- Compose methods with `forEachArtifactOf(...)` utility

- Add required `@Nonnull` annotations

  1. … 1 more file in changeset.
Polish `GenerateModuleMetadata`

- Format document

- Extract `publication()` accessor

- Reorder `generateTo` parameters to improve prose

- Compose methods with `forEachArtifactOf(...)` utility

- Add required `@Nonnull` annotations

  1. … 1 more file in changeset.
Make `GenerateModuleMetadata` `onlyIf` spec serializable

Make `GenerateModuleMetadata` `onlyIf` spec serializable

Let `ChecksumService` be injected into `GenerateModuleMetadata`

For compatibility with the configuration cache.

  1. … 1 more file in changeset.
Let `ChecksumService` be injected into `GenerateModuleMetadata`

For compatibility with the configuration cache.

  1. … 1 more file in changeset.
Give ability to opt-out of the build id in GMM

Gradle Module Metadata by default contains a unique build identifier,

making the production of the file not reproducible.

With this commit, it is now possible to opt-out of the inclusion of this

build identifier in the produced metadata file.

Issue #11717

    • -0
    • +21
    ./org/gradle/api/publish/Publication.java
  1. … 11 more files in changeset.
Give ability to opt-out of the build id in GMM

Gradle Module Metadata by default contains a unique build identifier,

making the production of the file not reproducible.

With this commit, it is now possible to opt-out of the inclusion of this

build identifier in the produced metadata file.

Issue #11717

    • -0
    • +21
    ./org/gradle/api/publish/Publication.java
  1. … 11 more files in changeset.
Give ability to opt-out of the build id in GMM

Gradle Module Metadata by default contains a unique build identifier,

making the production of the file not reproducible.

With this commit, it is now possible to opt-out of the inclusion of this

build identifier in the produced metadata file.

Issue #11717

    • -0
    • +21
    ./org/gradle/api/publish/Publication.java
  1. … 11 more files in changeset.
Address compiler warnings in 'publishing' subproject

Address compiler warnings in 'publishing' subproject

Address compiler warnings in 'publishing' subproject

Use plugins DSL in Javadoc code snippets

  1. … 46 more files in changeset.
Use plugins DSL in Javadoc code snippets

  1. … 46 more files in changeset.
Revert "Configuration of build identifier"

This reverts commits ecb234a255f,

46d52bf8e7e10, 97e9694e12f.

    • -13
    • +0
    ./org/gradle/api/publish/Publication.java
  1. … 11 more files in changeset.
Revert "Make publication build identifier configurable"

This reverts commit ecb234a255f2af0abf9e06c282f9be4ee85d6014.

    • -13
    • +0
    ./org/gradle/api/publish/Publication.java
  1. … 7 more files in changeset.
Make publication build identifier configurable

This allows to set a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

    • -0
    • +13
    ./org/gradle/api/publish/Publication.java
  1. … 7 more files in changeset.
Make publication build identifier configurable

This allows to set a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

    • -0
    • +13
    ./org/gradle/api/publish/Publication.java
  1. … 7 more files in changeset.
Publication can configure the build identifier

This allows to use a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

    • -0
    • +13
    ./org/gradle/api/publish/Publication.java
  1. … 6 more files in changeset.
Make publication build identifier configurable

This allows to set a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

    • -0
    • +13
    ./org/gradle/api/publish/Publication.java
  1. … 7 more files in changeset.
Make publication build identifier configurable

This allows to set a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

    • -0
    • +13
    ./org/gradle/api/publish/Publication.java
  1. … 7 more files in changeset.
Make publication build identifier configurable

This allows to set a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

    • -0
    • +13
    ./org/gradle/api/publish/Publication.java
  1. … 6 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. … 36 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. … 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. … 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. … 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. … 44 more files in changeset.