integTest

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Improve publication warning message

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

* Clean up tests

  1. … 4 more files in changeset.
Do not change extension of published artifact based on pom packaging

We now publish the artifacts as they were defined in the build.

If the packaging and artifact extension should be aligned, this

can easily be done by adjusting the artifact extension when

building it (e.g. by utilizing jar.archiveExtension.set())

Before this change, Gradle Module Metadata was broken for artifacts

that were changed after the metadata file has been generated

(newly added 'MavenPublishPomPackagingJavaIntegTest' tests failed).

  1. … 2 more files in changeset.
Restore behavior of pom packaging changing the main artifact extension

This restores the behavior before #9445 (before 5.6) and with

that fixes #10555.

The behavior for non-jar packaging is still problematic and should

be changed for 6.0 as it leads to broken Gradle Module Metadata.

  1. … 1 more file in changeset.
Restore behavior of pom packaging changing the main artifact extension

This restores the behavior before #9445 (before 5.6) and with

that fixes #10555.

The behavior for non-jar packaging is still problematic and should

be changed for 6.0 as it leads to broken Gradle Module Metadata.

  1. … 1 more file in changeset.
Restore behavior of pom packaging changing the main artifact extension

This restores the behavior before #9445 (before 5.6) and with

that fixes #10555.

The behavior for non-jar packaging is still problematic and should

be changed for 6.0 as it leads to broken Gradle Module Metadata.

  1. … 1 more file 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. … 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.