Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -30
    • +30
    ./diagnostics/DependencyReportTaskIntegrationTest.groovy
    • -17
    • +17
    ./diagnostics/TaskReportTaskIntegrationTest.groovy
  1. … 871 more files in changeset.
Annotate integ tests failing with instant execution in :diagnostics

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -1
    • +30
    ./diagnostics/DependencyReportTaskIntegrationTest.groovy
    • -0
    • +17
    ./diagnostics/TaskReportTaskIntegrationTest.groovy
  1. … 3 more files in changeset.
Fix samples

* Typo in withSourcesJar() in one sample

* Java basic sample has issues creating javadoc with the asciidoclet

under recent java -> moved the with*Jars() include to another sample.

Issue #11140

    • -1
    • +1
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 5 more files in changeset.
Fix samples

* Typo in withSourcesJar() in one sample

* Java basic sample has issues creating javadoc with the asciidoclet

under recent java -> moved the with*Jars() include to another sample.

Issue #11140

    • -1
    • +1
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 5 more files in changeset.
Rename methods for javadoc and sources jar creation

The new name reflects better what happens exactly when the option is

activated on the java extension.

The publication part is only applicable when a publishing plugin is also

configured.

Issue #11140

    • -4
    • +4
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 25 more files in changeset.
Rename methods for javadoc and sources jar creation

The new name reflects better what happens exactly when the option is

activated on the java extension.

The publication part is only applicable when a publishing plugin is also

configured.

Issue #11140

    • -4
    • +4
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 24 more files in changeset.
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.
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.
Fix environment specific test expectation

    • -2
    • +2
    ./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.
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.
Improve outgoing variant report

* Add capabilities information to the report

    • -0
    • +38
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Adjust tests and samples to new metadata sources defaults

    • -6
    • +0
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
    • -2
    • +0
    ./diagnostics/DependencyInsightReportVariantDetailsIntegrationTest.groovy
  1. … 94 more files in changeset.
Improve rendering of artifacts in outgoing variants report

This commit changes how artifacts are rendered, so that if they

are associated with a type (either explicit or derived), we show

the corresponding `artifactType` attribute.

This helps understanding a bit what can happen in an Android build

where multiple variants may have the same attributes, but only

differ on the artifact type derived from the artifacts carried

by the variant.

    • -17
    • +75
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix test for Windows

    • -17
    • +17
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
Fix test expectation

    • -0
    • +1
    ./diagnostics/TaskReportTaskIntegrationTest.groovy
Add an outgoing variants report

This commit introduces an `outgoingVariants` task which generates

a report of the outgoing variants of a project. This is useful

for debugging and understanding variant aware resolution.

It becomes possible for a plugin author to understand what variants

are already produced by a project based on the plugins applied, and

what artifacts are attached to what variant.

    • -0
    • +342
    ./diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 9 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
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
    • -23
    • +23
    ./diagnostics/DependencyInsightReportVariantDetailsIntegrationTest.groovy
  1. … 45 more files in changeset.
Exclude deprecated configurations from reports

    • -0
    • +1
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
    • -0
    • +76
    ./diagnostics/DependencyReportTaskIntegrationTest.groovy
  1. … 6 more files in changeset.
Remove utilisation of *-jars usage values

    • -5
    • +60
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
    • -3
    • +8
    ./diagnostics/DependencyInsightReportVariantDetailsIntegrationTest.groovy
  1. … 54 more files in changeset.
Let dependency (insight) report tests not use deprecated configurations

    • -42
    • +52
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
    • -16
    • +16
    ./diagnostics/DependencyReportTaskIntegrationTest.groovy
Sort module selectors

This commit reworks module selectors so that they are sorted

in an order which reduces the cost of module selection. We

make sure to put local (project) selectors first, then we

use selectors from locks (if any).

The next selectors are "latest" version selectors because

even if they are dynamic, they are likely to "win" selection.

Then, exact version selectors are sorted by version descending

, and last we add dynamic version selectors.

    • -6
    • +6
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
  1. … 19 more files in changeset.
Partial ordering of module selectors

With this commit, we do a partial sort on the selectors, where we place

the dynamic selectors at the end compared to the other ones.

This allows a more efficient resolution in some corner cases but is

mostly preparation work for follow up changes.

    • -1
    • +1
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
  1. … 7 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -0
    • +5
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
    • -0
    • +1
    ./diagnostics/DependencyInsightReportVariantDetailsIntegrationTest.groovy
  1. … 26 more files in changeset.
Rename category attribute

Attribute is now `org.gradle.category` and the constant is named

VARIANT_CATEGORY.

The removal of the "component" part of the name was to clarify to what

the category applies.

    • -101
    • +101
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
    • -15
    • +15
    ./diagnostics/DependencyInsightReportVariantDetailsIntegrationTest.groovy
  1. … 25 more files in changeset.
Fix rebase glitches

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