integTest

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Updates to terminology for clarity

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

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

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

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

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

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

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

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

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

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

- `inheritStrictConstraints` -> `inheritStrictVersions`

- `notInheritStrictConstraints` -> `doNotInheritStrictVersions`

  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).

  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).

  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).

  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).

  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).

  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).

  1. … 77 more files in changeset.
Add API for silencing publication warnings

* API is per variant or all warnings

Fixes #9378

Fixes #10431

  1. … 6 more files in changeset.
Add API for silencing publication warnings

* API is per variant or all warnings

Fixes #9378

Fixes #10431

  1. … 6 more files in changeset.
Add API for silencing publication warnings

* API is per variant or all warnings

Fixes #9378

Fixes #10431

  1. … 6 more files in changeset.
Add API for silencing publication warnings

* API is per variant or all warnings

Fixes #9378

Fixes #10431

  1. … 6 more files in changeset.
Add API for silencing publication warnings

* API is per variant or all warnings

Fixes #9378

Fixes #10431

  1. … 6 more files in changeset.
Add API for silencing publication warnings

* API is per variant or all warnings

Fixes #9378

Fixes #10431

  1. … 6 more files in changeset.
Add API for silencing publication warnings

* API is per variant or all warnings

Fixes #9378

Fixes #10431

  1. … 6 more files in changeset.
Rework publication compatibility warnings

* Group by variant

* Isolate variant level warnings

Issue #9378

  1. … 5 more files in changeset.
Rework publication compatibility warnings

* Group by variant

* Isolate variant level warnings

Issue #9378

  1. … 5 more files in changeset.
Rework publication compatibility warnings

* Group by variant

* Isolate variant level warnings

Issue #9378

  1. … 5 more files in changeset.
Rework publication compatibility warnings

* Group by variant

* Isolate variant level warnings

Issue #9378

  1. … 5 more files in changeset.
Rework publication compatibility warnings

* Group by variant

* Isolate variant level warnings

Issue #9378

  1. … 5 more files in changeset.
Rework publication compatibility warnings

* Group by variant

* Isolate variant level warnings

Issue #9378

  1. … 5 more files in changeset.
Rework publication compatibility warnings

* Group by variant

* Isolate variant level warnings

Issue #9378

  1. … 5 more files in changeset.
Add AdhocSoftwareComponent.withVariantsFromConfiguration() API

  1. … 8 more files in changeset.
Add test coverage for artifact selectors in GMM

  1. … 5 more files in changeset.
Add test coverage for artifact selectors in GMM

  1. … 8 more files in changeset.
Deprecate the maven/ivy plugins

This commit introduces a deprecation warning for the `maven` plugin.

Because there's no such thing as an `ivy` plugin, we also deprecate

the _use_ of the `uploadArchives` task, which corresponds to uploading

with `ivy`, but is defined in the `base` plugin that we cannot

deprecate.

  1. … 9 more files in changeset.