internal

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Revert "Revert "Merge pull request #9840 from gradle/lptr/files/simplify-file-matchers""

This reverts commit 669ec8c0211ad7e36ec4a91921e2da5da8619bef.

    • -279
    • +0
    ./file/FileCollectionIntegrationTest.groovy
  1. … 324 more files in changeset.
Revert "Merge pull request #9840 from gradle/lptr/files/simplify-file-matchers"

This reverts commit 72dc39d9784910196e7840ac35317bc46ef4c4a1, reversing

changes made to 69ffd7ea87b343cb6f0f03b947b7605a5bea02b1.

    • -0
    • +279
    ./file/FileCollectionIntegrationTest.groovy
  1. … 324 more files in changeset.
Rename :files project to :file-collections

    • -279
    • +0
    ./file/FileCollectionIntegrationTest.groovy
  1. … 243 more files in changeset.
Rename :files project to :file-collections

    • -279
    • +0
    ./file/FileCollectionIntegrationTest.groovy
  1. … 243 more files in changeset.
Rename :files project to :file-collections

    • -279
    • +0
    ./file/FileCollectionIntegrationTest.groovy
  1. … 242 more files in changeset.
Add `FileCollection.getElements()`, which returns a view of the collection elements as a `Provider<Set<FileSystemLocation>>`. This can then be used, for example, as an input to a `Property`.

    • -0
    • +42
    ./file/FileCollectionIntegrationTest.groovy
  1. … 3 more files in changeset.
Add `FileCollection.getElements()`, which returns a view of the collection elements as a `Provider<Set<FileSystemLocation>>`. This can then be used, for example, as an input to a `Property`.

    • -0
    • +42
    ./file/FileCollectionIntegrationTest.groovy
  1. … 7 more files in changeset.
Add `FileCollection.getElements()`, which returns a view of the collection elements as a `Provider<Set<FileSystemLocation>>`. This can then be used, for example, as an input to a `Property`.

    • -0
    • +42
    ./file/FileCollectionIntegrationTest.groovy
  1. … 3 more files in changeset.
Add `FileCollection.getElements()`, which returns a view of the collection elements as a `Provider<Set<FileSystemLocation>>`. This can then be used, for example, as an input to a `Property`.

    • -0
    • +42
    ./file/FileCollectionIntegrationTest.groovy
  1. … 7 more files in changeset.
Minor tweak to error message.

    • -2
    • +2
    ./file/FileCollectionIntegrationTest.groovy
  1. … 1 more file in changeset.
Minor tweak to error message.

    • -2
    • +2
    ./file/FileCollectionIntegrationTest.groovy
  1. … 1 more file in changeset.
Minor tweak to error message.

    • -2
    • +2
    ./file/FileCollectionIntegrationTest.groovy
  1. … 1 more file in changeset.
Minor tweak to error message.

    • -2
    • +2
    ./file/FileCollectionIntegrationTest.groovy
  1. … 1 more file in changeset.
Minor tweak to error message.

    • -2
    • +2
    ./file/FileCollectionIntegrationTest.groovy
  1. … 1 more file in changeset.
Add `HasConfigurableValue.disallowChanges()` which disallows changes to a `Property` or `ConfigurableFileCollection` without finalizing the value.

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

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

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

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

    • -0
    • +25
    ./file/FileCollectionIntegrationTest.groovy
  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
    • +87
    ./file/FileCollectionIntegrationTest.groovy
  1. … 14 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
    • +87
    ./file/FileCollectionIntegrationTest.groovy
  1. … 14 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
    • +87
    ./file/FileCollectionIntegrationTest.groovy
  1. … 14 more files in changeset.
int tests for previous commit.

    • -2
    • +42
    ./file/FileCollectionIntegrationTest.groovy
  1. … 1 more file in changeset.
Change the implementation of `ConfigurableFileCollection.finalizeValue()` so that only the locations are finalized, not the set of files.

For example, when a collection contains a `FileTree` that is backed by a directory, then changes to the directory are reflected in the contents of the collection. In this way, a finalized file collection is basically a finalized set of file system roots, not a finalized set of files.

    • -5
    • +89
    ./file/FileCollectionIntegrationTest.groovy
  1. … 4 more files in changeset.
Change the implementation of `ConfigurableFileCollection.finalizeValue()` so that only the locations are finalized, not the set of files.

For example, when a collection contains a `FileTree` that is backed by a directory, then changes to the directory are reflected in the contents of the collection. In this way, a finalized file collection is basically a finalized set of file system roots, not a finalized set of files.

    • -5
    • +49
    ./file/FileCollectionIntegrationTest.groovy
  1. … 3 more files in changeset.
Change the implementation of `ConfigurableFileCollection.finalizeValue()` so that only the locations are finalized, not the set of files.

For example, when a collection contains a `FileTree` that is backed by a directory, then changes to the directory are reflected in the contents of the collection. In this way, a finalized file collection is basically a finalized set of file system roots, not a finalized set of files.

    • -5
    • +89
    ./file/FileCollectionIntegrationTest.groovy
  1. … 4 more files in changeset.
Change the implementation of `ConfigurableFileCollection.finalizeValue()` so that only the locations are finalized, not the set of files.

For example, when a collection contains a `FileTree` that is backed by a directory, then changes to the directory are reflected in the contents of the collection. In this way, a finalized file collection is basically a finalized set of file system roots, not a finalized set of files.

    • -5
    • +89
    ./file/FileCollectionIntegrationTest.groovy
  1. … 4 more files in changeset.
Change the implementation of `ConfigurableFileCollection.finalizeValue()` so that only the locations are finalized, not the set of files.

For example, when a collection contains a `FileTree` that is backed by a directory, then changes to the directory are reflected in the contents of the collection. In this way, a finalized file collection is basically a finalized set of file system roots, not a finalized set of files.

    • -5
    • +89
    ./file/FileCollectionIntegrationTest.groovy
  1. … 4 more files in changeset.
Change the implementation of `ConfigurableFileCollection.finalizeValue()` so that only the locations are finalized, not the set of files.

For example, when a collection contains a `FileTree` that is backed by a directory, then changes to the directory are reflected in the contents of the collection. In this way, a finalized file collection is basically a finalized set of file system roots, not a finalized set of files.

    • -5
    • +89
    ./file/FileCollectionIntegrationTest.groovy
  1. … 4 more files in changeset.
Change the implementation of `ConfigurableFileCollection.finalizeValue()` so that only the locations are finalized, not the set of files.

For example, when a collection contains a `FileTree` that is backed by a directory, then changes to the directory are reflected in the contents of the collection. In this way, a finalized file collection is basically a finalized set of file system roots, not a finalized set of files.

    • -5
    • +89
    ./file/FileCollectionIntegrationTest.groovy
  1. … 4 more files in changeset.