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
    ./diagnostics/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
    ./diagnostics/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
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
  1. … 10 more files in changeset.
Make Javadoc and sources primary variants without dependencies

    • -20
    • +32
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 15 more files in changeset.
Make Javadoc and sources primary variants without dependencies

    • -20
    • +32
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 15 more files in changeset.
Make Javadoc and sources primary variants without dependencies

    • -20
    • +32
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 15 more files in changeset.
Make Javadoc and sources primary variants without dependencies

    • -20
    • +32
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 15 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

    • -20
    • +86
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 34 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

    • -20
    • +86
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 34 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

    • -20
    • +86
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 35 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

    • -20
    • +86
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 34 more files in changeset.
Fix environment specific test expectation

    • -2
    • +2
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
Fix environment specific test expectation

    • -2
    • +2
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
Fix environment specific test expectation

    • -2
    • +2
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
Expect 'javadoc' and 'sources' variants in outgoing variants report

    • -0
    • +40
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
Expect 'javadoc' and 'sources' variants in outgoing variants report

    • -0
    • +40
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
Expect 'javadoc' and 'sources' variants in outgoing variants report

    • -0
    • +40
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
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
    ./diagnostics/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
    ./diagnostics/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
    ./diagnostics/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
    ./diagnostics/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
    ./diagnostics/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
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
  1. … 23 more files in changeset.
Make the default capability explicit in report

* When reporting a variant that only has the default capability, it is

now explicit and flagged as the default one.

    • -17
    • +26
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 1 more file in changeset.
Make the default capability explicit in report

* When reporting a variant that only has the default capability, it is

now explicit and flagged as the default one.

    • -17
    • +26
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 1 more file in changeset.
Make the default capability explicit in report

* When reporting a variant that only has the default capability, it is

now explicit and flagged as the default one.

    • -17
    • +26
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 1 more file in changeset.
Improve outgoing variant report

* Add capabilities information to the report

    • -0
    • +38
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Improve outgoing variant report

* Add capabilities information to the report

    • -0
    • +38
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Improve outgoing variant report

* Add capabilities information to the report

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

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