Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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.

  1. … 9 more files in changeset.
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.

  1. … 9 more files in changeset.
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.

  1. … 9 more files in changeset.
Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

The `TestFixturesPlugin` of our build has been simplified to leverage the native

test fixtures capabilities. Some noticeable changes:

- the `testFixtures` extension has been replaced with regular dependency declaration

- dependencies on test fixtures are now declared using the `testFixtures` keyword

- test fixtures properly declare an API and an implementation, meaning that the

implementation dependencies of test fixtures no longer leak into the compile

classpath of consumers (in particular tests)

  1. … 88 more files in changeset.
WIP: Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

  1. … 84 more files in changeset.
WIP: Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

  1. … 84 more files in changeset.
WIP: Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

  1. … 84 more files in changeset.
Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

The `TestFixturesPlugin` of our build has been simplified to leverage the native

test fixtures capabilities. Some noticeable changes:

- the `testFixtures` extension has been replaced with regular dependency declaration

- dependencies on test fixtures are now declared using the `testFixtures` keyword

- test fixtures properly declare an API and an implementation, meaning that the

implementation dependencies of test fixtures no longer leak into the compile

classpath of consumers (in particular tests)

  1. … 88 more files in changeset.
WIP: Dogfood native test fixtures

This commit replaces our custom test fixtures with the native "Java test fixtures".

  1. … 84 more files in changeset.
Cleanup some unnessasary changes after depricate http changes

Signed-off-by: Jonathan Leitschuh <Jonathan.Leitschuh@gmail.com>

    • -12
    • +0
    ./DetailedModelReportIntegrationTest.groovy
  1. … 10 more files in changeset.
Fix integration tests failing due to new dperication

Signed-off-by: Jonathan Leitschuh <Jonathan.Leitschuh@gmail.com>

    • -0
    • +12
    ./DetailedModelReportIntegrationTest.groovy
  1. … 10 more files in changeset.
Fix integ tests after new buit-in task

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

  1. … 3 more files in changeset.
Externalize samples testing infrastructure

This change replaces UserGuideSamplesRunner with an external library

called sample-check. Sample discovery, execution, and normalization

is delegated to this library, with some custom normalizers remaining

in the Gradle codebase.

Samples output has become co-located with the sample code. Samples tests

must be run with Java 8+.

  1. … 782 more files in changeset.
Bridge tasks into software mode lazily

Only initialize the software model bridging if the user

either uses the `model {}` block or explicitly applies

a rule-based plugin.

Placeholder tasks are now implemented in the task container

directly instead of using the software model. They are also

deprecated as they add a lot of complexity for no gain beyond

what `createLater {}` already offers.

    • -24
    • +24
    ./ModelReportIntegrationTest.groovy
  1. … 29 more files in changeset.
Fix model report and user guide samples integ tests for #dependent-components

  1. … 4 more files in changeset.
Fix test so that it doesn't leak test output file

    • -2
    • +4
    ./DetailedModelReportIntegrationTest.groovy
Fix integration test

+review REVIEW-5921

Don't write the null character in the model report for default `char` values.

This is asking for trouble with downstream systems.

  1. … 1 more file in changeset.
Replace `@BinaryType` and `@LanguageType` with `@ComponentType`

The original annotations have been retained for the purpose of

deprecation but they no longer work.

  1. … 64 more files in changeset.
Replaced most usages of `BinaryTypeBuilder` and `ComponentTypeBuilder` with the more general `TypeBuilder`.

  1. … 48 more files in changeset.
Do not explicitly check for tasks in model report

When tasks are not an important part of the report, do not check for

them.

+review REVIEW-5771

    • -91
    • +44
    ./ModelReportIntegrationTest.groovy
Simplify test

+review REVIEW-5771

    • -10
    • +10
    ./ModelReportIntegrationTest.groovy
Expose the corresponding property when finding initializer for a node

The point is to be able to use the information whether or not the

scalar collection property is writable or not. In the writable case

(where there is a setCollection() method), de default value of the

collection should be null. Where there’s only a getCollection() method

declaring the property, the default value should be an empty

collection. The mode report should display these values, too.

+review REVIEW-5769

  1. … 10 more files in changeset.
Model report sensible value for node whose toString() returns null

+review REVIEW-5771

    • -0
    • +19
    ./ModelReportIntegrationTest.groovy
  1. … 3 more files in changeset.
Changed the model report to show the target of a model element reference.

This also means that the model report can now deal with cycles in the model graph.

    • -2
    • +31
    ./ModelReportIntegrationTest.groovy
  1. … 3 more files in changeset.
Scalar properties values always reported, including when unset

+review REVIEW-5771

    • -0
    • +110
    ./ModelReportIntegrationTest.groovy
  1. … 6 more files in changeset.
Report managed properties values of scalar collections when unset or null

+review REVIEW-5769

  1. … 1 more file in changeset.
Add test for null properties in model report

Managed properties must be displayed in the model report even if they

have a value of null. Their type must be displayed, too.

+review REVIEW-5738

    • -0
    • +33
    ./ModelReportIntegrationTest.groovy
  1. … 4 more files in changeset.
Fix test

We only have @Hidden now, no @Service.

Added support for number narrowing in the converter, needed because Groovy doesn't when there's a setter overload

+review REVIEW-5672

    • -11
    • +11
    ./ModelReportIntegrationTest.groovy
  1. … 4 more files in changeset.