collections

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fixes.

  1. … 4 more files in changeset.
Fixes.

  1. … 4 more files in changeset.
Fixes.

Fixes.

When a strict `Property` is read, finalize all properties whose values are used to calculate the property's final value.

  1. … 40 more files in changeset.
When a strict `Property` is read, finalize all properties whose values are used to calculate the property's final value.

  1. … 40 more files in changeset.
When a strict `Property` is read, finalize all properties whose values are used to calculate the property's final value.

  1. … 40 more files in changeset.
Report the chain of properties from which a mapped `Provider` has come from, when the value is missing.

  1. … 22 more files in changeset.
Report the chain of properties from which a mapped `Provider` has come from, when the value is missing.

  1. … 30 more files in changeset.
Report the chain of properties from which a mapped `Provider` has come from, when the value is missing.

  1. … 29 more files in changeset.
Report the chain of properties from which a mapped `Provider` has come from, when the value is missing.

  1. … 30 more files in changeset.
Fix for previous commit.

  1. … 1 more file in changeset.
Fix for previous commit.

  1. … 1 more file in changeset.
Report the chain of properties from which an element of a `ListProperty`, `SetProperty` or entry of a `MapProperty` come from, when the value is missing.

  1. … 7 more files in changeset.
Report the chain of properties from which an element of a `ListProperty`, `SetProperty` or entry of a `MapProperty` come from, when the value is missing.

  1. … 7 more files in changeset.
Report the chain of properties from which an element of a `ListProperty`, `SetProperty` or entry of a `MapProperty` come from, when the value is missing.

  1. … 7 more files in changeset.
Fix for previous commit.

  1. … 1 more file in changeset.
Report the chain of properties from which the value of a `ListProperty`, `SetProperty` and `MapProperty` come from, when the value is missing.

  1. … 21 more files in changeset.
Report the chain of properties from which the value of a `ListProperty`, `SetProperty` and `MapProperty` come from, when the value is missing.

  1. … 21 more files in changeset.
Report the chain of properties from which the value of a `ListProperty`, `SetProperty` and `MapProperty` come from, when the value is missing.

  1. … 21 more files in changeset.
Report the chain of properties from which the value of a `ListProperty`, `SetProperty` and `MapProperty` come from, when the value is missing.

  1. … 21 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 19 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 19 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 34 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 34 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 34 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 34 more files in changeset.
Apply DSL decoratation to the elements created by containers created using `ObjectFactory.domainObjectContainer()` and for read-only managed properties.

    • -0
    • +53
    ./DefaultDomainObjectCollectionFactoryTest.groovy
  1. … 9 more files in changeset.
Apply DSL decoratation to the elements created by containers created using `ObjectFactory.domainObjectContainer()` and for read-only managed properties.

    • -0
    • +53
    ./DefaultDomainObjectCollectionFactoryTest.groovy
  1. … 9 more files in changeset.
Emit build operations around container callback executions (core and dependencyMgmt containers) (#7734)

* Decorate taskcontainer callbacks to track application id

* Decorate plugin container callbacks

* Decorate repositoryContainer callbacks

* Decoreate configurations and configuration.dependencies container callbacks

* Decorate artifactTypesDecorator callbacks

* Dont emit build ops for internal declared callbacks

* Provide usercode context in beforeResolve / afterResolve callbacks

* keep compatibility for nebula.dependency-recommender plugin

* Put domain collection callback build ops behind feature toggle

* Decorate Provider.configure() methods

* Simplify container callback filtering and decoration

Previously, we had three classes collaborating to achieve this but now this is inlined into effectively one. While this creates a more complex implementation, that is still rather simple, it avoids the more problematic complexity of a complicated relationship between the three implementations that also required extra state and details to be propagated through all of the collections.

    • -88
    • +0
    ./BroadcastingCollectionEventRegisterSpec.groovy
    • -0
    • +98
    ./DefaultCollectionEventRegisterSpec.groovy
  1. … 69 more files in changeset.