DependencyInsightReportTaskIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Revert "Do not emit deprecation warning for deprecated 'force'"

This reverts commit 1db54192db6ef9af5c2fd6b227004eed9a27c07f.

    • -0
    • +2
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 10 more files in changeset.
Do not emit deprecation warning for deprecated 'force'

Nagging for this deprecation will only start with 6.1 to ease

the migration from 'force' to 'strictly'.

    • -2
    • +0
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 10 more files in changeset.
Do not emit deprecation warning for deprecated 'force'

Nagging for this deprecation will only start with 6.1 to ease

the migration from 'force' to 'strictly'.

    • -2
    • +0
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 10 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +2
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 12 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +2
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 12 more files in changeset.
Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

    • -0
    • +2
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 12 more files in changeset.
Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

    • -0
    • +2
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 23 more files in changeset.
Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

    • -0
    • +2
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 18 more files in changeset.
Deprecated `force` on first-level dependencies

This commit deprecates using `force` in favor of using the

new "strictly" behavior. The "force" flag is still used

internally, in particular in case of virtual platforms, but

its usage should be discouraged as we have a solution which

is better now.

    • -0
    • +2
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 23 more files in changeset.
Adjust test fixtures and test to ivy behavior changes

    • -2
    • +2
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 38 more files in changeset.
Fixes

    • -2
    • +2
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 31 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -6
    • +0
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 95 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -4
    • +0
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -4
    • +0
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -4
    • +0
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 29 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

    • -2
    • +0
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 10 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

    • -2
    • +0
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 10 more files in changeset.
Remove special repository default behavior with GRADLE_METADATA flag

The default behavior is now that we look for 'traditional' metadata

first, but find Gradle metadata if a marker is present.

We won't look for anything else if the 'traditional' metadata is not

found. This increases performance for the cases where one repository

is asked for many modules it does not contain.

Users can opt into different behavior using `gradleMetadata()` or

`artifact()` when defining their repositories.

    • -2
    • +0
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 10 more files in changeset.
WIP

    • -55
    • +55
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryelements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -133
    • +133
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryElements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -133
    • +133
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryelements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -133
    • +133
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryElements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -133
    • +133
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryElements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -55
    • +55
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryelements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -133
    • +133
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryElements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -133
    • +133
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 46 more files in changeset.
Rename format attribute and clean up values

Attribute is now org.gradle.libraryelements and only applied

to variants having the org.gradle.category at library.

This means that values related to platforms or document in the

former format attribute are removed.

    • -133
    • +133
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 46 more files in changeset.
WIP

    • -5
    • +60
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 4 more files in changeset.
Exclude deprecated configurations from reports

    • -0
    • +1
    ./DependencyInsightReportTaskIntegrationTest.groovy
  1. … 7 more files in changeset.
Exclude deprecated configurations from reports

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