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.
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.
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. … 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.
Remove trailing space in error message

And pay the price with tons of whitespace changes...

    • -11
    • +11
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
  1. … 10 more files in changeset.
Remove trailing space in error message

And pay the price with tons of whitespace changes...

    • -11
    • +11
    ./diagnostics/DependencyInsightReportTaskIntegrationTest.groovy
  1. … 10 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.
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.