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

    • -3
    • +3
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 70 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.

    • -3
    • +3
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 70 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.
Use instantiator for DSL objects created through SoftwareComponentFactory

To have a better and consistent DSL experience when using:

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

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

  1. … 8 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.
Document ability to suppress publication warnings

* Includes a rename from silence* to suppress* as used in other APIs,

including @SuppressWarnings

Fixes #10467

  1. … 10 more files in changeset.
Document ability to suppress publication warnings

* Includes a rename from silence* to suppress* as used in other APIs,

including @SuppressWarnings

Fixes #10467

  1. … 10 more files in changeset.
Document ability to suppress publication warnings

* Includes a rename from silence* to suppress* as used in other APIs,

including @SuppressWarnings

Fixes #10467

  1. … 10 more files in changeset.
Document ability to suppress publication warnings

* Includes a rename from silence* to suppress* as used in other APIs,

including @SuppressWarnings

Fixes #10467

  1. … 10 more files in changeset.
Tweaks in metadata warnings headers and footers

  1. … 4 more files in changeset.
Tweaks in metadata warnings headers and footers

  1. … 4 more files in changeset.
Rename API for silencing publication warnings

* New name indicates better that these warnings are about the non Gradle

metadata formats.

  1. … 5 more files in changeset.
Rename API for silencing publication warnings

* New name indicates better that these warnings are about the non Gradle

metadata formats.

  1. … 5 more files in changeset.
Rename API for silencing publication warnings

* New name indicates better that these warnings are about the non Gradle

metadata formats.

  1. … 5 more files in changeset.
Improve publication warning message

* Clarify this impacts POM and Ivy format, not Gradle Module Metadata

* Clean up tests

  1. … 4 more files in changeset.
Improve publication warning message

* Clarify this impacts POM and Ivy format, not Gradle Module Metadata

* Clean up tests

  1. … 4 more files in changeset.
Improve publication warning message

* Clarify this impacts POM and Ivy format, not Gradle Module Metadata

* Clean up tests

  1. … 4 more files in changeset.
Improve publication warning message

* Clarify this impacts POM and Ivy format, not Gradle Module Metadata

* Clean up tests

  1. … 4 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -3
    • +3
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 31 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -3
    • +3
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 31 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -3
    • +3
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 31 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -3
    • +3
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 31 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -3
    • +3
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 31 more files in changeset.
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

    • -3
    • +3
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 30 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -13
    • +10
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 77 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -13
    • +10
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 79 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -13
    • +10
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 77 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -13
    • +10
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 77 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -13
    • +10
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 77 more files in changeset.
Rework `forSubgraph` as implied by `strictly`

This commit removes a dedicated `forSubgraph` flag

on version constraints, so that it is _implied_ by

strict version constraints. This simplifies the behavior

of `strictly`, making it closer to the intuitive semantics,

while maintaining the ability to fail the build if a

consumer brings an incompatible version in the graph.

As a consequence, _strict dependencies_ now express that

the producer preference overrides whatever is found in

its own dependency graph. It is closer to the "nearest

first" semantics of Maven, while not having its drawbacks

(ordering in particular).

    • -13
    • +10
    ./gradle/api/publish/ivy/IvyGradleModuleMetadataPublishIntegrationTest.groovy
  1. … 77 more files in changeset.