OutgoingVariantsReportTaskIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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
    ./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
    ./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
    ./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
    ./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
    ./OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 24 more files in changeset.
Make Javadoc and sources primary variants without dependencies

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

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

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

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

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

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

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

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

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

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

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

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

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

    • -0
    • +40
    ./OutgoingVariantsReportTaskIntegrationTest.groovy
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
    ./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
    ./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
    ./OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 1 more file in changeset.
Improve outgoing variant report

* Add capabilities information to the report

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

* Add capabilities information to the report

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

* Add capabilities information to the report

    • -0
    • +38
    ./OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 2 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
    ./OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 2 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
    ./OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 2 more files in changeset.
Fix test for Windows

    • -17
    • +17
    ./OutgoingVariantsReportTaskIntegrationTest.groovy
Fix test for Windows

    • -17
    • +17
    ./OutgoingVariantsReportTaskIntegrationTest.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
    ./OutgoingVariantsReportTaskIntegrationTest.groovy
  1. … 2 more files in changeset.