Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Some refactoring of the collection and map property implementations.

  1. … 3 more files in changeset.
Some refactoring of the collection and map property implementations.

  1. … 3 more files in changeset.
Consolidated some `FileSystemLocation` implementations and added some unit test coverage.

  1. … 11 more files in changeset.
Consolidated some `FileSystemLocation` implementations and added some unit test coverage.

  1. … 11 more files in changeset.
Add missing `value(T)` and `value(Provider<T>)` methods to various property types.

  1. … 15 more files in changeset.
Add missing `value(T)` and `value(Provider<T>)` methods to various property types.

  1. … 15 more files in changeset.
Add missing `value(T)` and `value(Provider<T>)` methods to various property types.

  1. … 15 more files in changeset.
Add `Provider.orElse()` methods, to use the value of the provider or some alternative if not present.

  1. … 6 more files in changeset.
Add `Provider.orElse()` methods, to use the value of the provider or some alternative if not present.

  1. … 6 more files in changeset.
Renamed class and associated unit test.

    • -258
    • +0
    ./DefaultPropertyStateTest.groovy
    • -0
    • +258
    ./DefaultPropertyTest.groovy
  1. … 8 more files in changeset.
Renamed class and associated unit test.

    • -258
    • +0
    ./DefaultPropertyStateTest.groovy
    • -0
    • +258
    ./DefaultPropertyTest.groovy
  1. … 8 more files in changeset.
Add `HasConfigurableValue.disallowChanges()` which disallows changes to a `Property` or `ConfigurableFileCollection` without finalizing the value.

  1. … 8 more files in changeset.
Add `HasConfigurableValue.disallowChanges()` which disallows changes to a `Property` or `ConfigurableFileCollection` without finalizing the value.

  1. … 8 more files in changeset.
Add `HasConfigurableValue.disallowChanges()` which disallows changes to a `Property` or `ConfigurableFileCollection` without finalizing the value.

  1. … 8 more files in changeset.
Add `HasConfigurableValue.disallowChanges()` which disallows changes to a `Property` or `ConfigurableFileCollection` without finalizing the value.

  1. … 8 more files in changeset.
Add `HasConfigurableValue.disallowChanges()` which disallows changes to a `Property` or `ConfigurableFileCollection` without finalizing the value.

  1. … 8 more files in changeset.
Implicitly finalize the value of task properties with type `ConfigurableFileCollection` when task execution commences, as is done for `Property` types.

  1. … 12 more files in changeset.
Implicitly finalize the value of task properties with type `ConfigurableFileCollection` when task execution commences, as is done for `Property` types.

  1. … 12 more files in changeset.
Implicitly finalize the value of task properties with type `ConfigurableFileCollection` when task execution commences, as is done for `Property` types.

  1. … 12 more files in changeset.
WIP

  1. … 21 more files in changeset.
Move managed factories to a registry

  1. … 38 more files in changeset.
Move managed factories to a registry

  1. … 39 more files in changeset.
Move managed factories to a registry

  1. … 40 more files in changeset.
Move managed factories to a registry

  1. … 40 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

  1. … 9 more files in changeset.