Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove unnecessary @Unroll annotations from "core"

  1. … 121 more files in changeset.
Remove unnecessary @Unroll annotations from "core"

  1. … 121 more files in changeset.
Remove unnecessary @Unroll annotations from "core"

  1. … 121 more files in changeset.
Remove unnecessary @Unroll annotations from "core"

  1. … 121 more files in changeset.
Remove unnecessary @Unroll annotations from "core"

  1. … 121 more files in changeset.
fixes

  1. … 6 more files in changeset.
fixes

  1. … 6 more files in changeset.
fixes

  1. … 6 more files in changeset.
fixes

  1. … 6 more files in changeset.
Remove `FileResolver.getPatternSetFactory()` as this was only used to carry around the factory service and never used by the resolvers themselves. Instead, pass the factory around as a service.

  1. … 51 more files in changeset.
Remove `FileResolver.getPatternSetFactory()` as this was only used to carry around the factory service and never used by the resolvers themselves. Instead, pass the factory around as a service.

  1. … 50 more files in changeset.
Remove `FileResolver.getPatternSetFactory()` as this was only used to carry around the factory service and never used by the resolvers themselves. Instead, pass the factory around as a service.

  1. … 50 more files in changeset.
Remove `FileResolver.getPatternSetFactory()` as this was only used to carry around the factory service and never used by the resolvers themselves. Instead, pass the factory around as a service.

  1. … 51 more files in changeset.
Move instantiation of the various Property instances behind a factory interface.

  1. … 18 more files in changeset.
Move instantiation of the various Property instances behind a factory interface.

  1. … 18 more files in changeset.
Move instantiation of the various Property instances behind a factory interface.

  1. … 18 more files in changeset.
Move instantiation of the various Property instances behind a factory interface.

  1. … 18 more files in changeset.
Move instantiation of the various Property instances behind a factory interface.

  1. … 18 more files in changeset.
Move instantiation of the various Property instances behind a factory interface.

  1. … 18 more files in changeset.
Move instantiation of the various Property instances behind a factory interface.

  1. … 18 more files in changeset.
Fix for previous.

  1. … 5 more files in changeset.
Fix for previous.

  1. … 5 more files in changeset.
Add `HasConfigurableValue.disallowUnsafeRead()` to allow plugins to switch lazy instances to 'strict' behaviour wrt reads.

In this commit, a strict `Property` disallows reads until the owning project's `afterEvaluate` starts. This is not implemented for `FileCollection` yet.

  1. … 35 more files in changeset.
Add `HasConfigurableValue.disallowUnsafeRead()` to allow plugins to switch lazy instances to 'strict' behaviour wrt reads.

In this commit, a strict `Property` disallows reads until the owning project's `afterEvaluate` starts. This is not implemented for `FileCollection` yet.

  1. … 35 more files in changeset.
Add `HasConfigurableValue.disallowUnsafeRead()` to allow plugins to switch lazy instances to 'strict' behaviour wrt reads.

In this commit, a strict `Property` disallows reads until the owning project's `afterEvaluate` starts. This is not implemented for `FileCollection` yet.

  1. … 35 more files in changeset.
Fixes for previous commit.

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