FileResolutionIntegrationTest.groovy

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

    • -1
    • +1
    ./FileResolutionIntegrationTest.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.

    • -1
    • +1
    ./FileResolutionIntegrationTest.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.

    • -1
    • +1
    ./FileResolutionIntegrationTest.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.

    • -1
    • +1
    ./FileResolutionIntegrationTest.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.

    • -1
    • +1
    ./FileResolutionIntegrationTest.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.

    • -1
    • +1
    ./FileResolutionIntegrationTest.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.

    • -1
    • +1
    ./FileResolutionIntegrationTest.groovy
  1. … 4 more files in changeset.
Changed `Directory` and `RegularFile` so that they do not extend `Provider<File>` as these types represent some immutable location, rather than some calculated value.

Also added `FileSystemLocation` as a common supertype for these types to allow a consumer to declare that they accept a directory or a file or any file system element.

    • -0
    • +4
    ./FileResolutionIntegrationTest.groovy
  1. … 14 more files in changeset.
Fixed `Project.file()` and `Project.files()` to properly handle `Directory` and `RegularFile`. Also fixed `Project.files()` when presented a `Path` instance. Added some test coverage and updated the Javadocs on `Project`.

    • -3
    • +45
    ./FileResolutionIntegrationTest.groovy
  1. … 6 more files in changeset.
Fix typos

    • -2
    • +2
    ./FileResolutionIntegrationTest.groovy
  1. … 1 more file in changeset.
Project.file now supports java.nio.file.Path instances.

    • -1
    • +17
    ./FileResolutionIntegrationTest.groovy
  1. … 3 more files in changeset.
Some fixes for changes to error messages.

    • -4
    • +4
    ./FileResolutionIntegrationTest.groovy
  1. … 2 more files in changeset.
Changed FileOrUriNotationParser so that it uses the standard error handling.

    • -2
    • +2
    ./FileResolutionIntegrationTest.groovy
  1. … 8 more files in changeset.
Project.file() no longer accepts arbitrary parameters, and throws an exception for anything it does not recognize. Previously, it would convert the value of `toString()` on these values.

    • -0
    • +56
    ./FileResolutionIntegrationTest.groovy
  1. … 8 more files in changeset.