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

This reverts commit 669ec8c0211ad7e36ec4a91921e2da5da8619bef.

    • -234
    • +0
  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
    • +234
  1. … 324 more files in changeset.
Rename :files project to :file-collections

    • -234
    • +0
  1. … 243 more files in changeset.
Remove some unused stuff.

    • -65
    • +0
  1. … 1 more file in changeset.
Separate out some shared behaviour from the `FileCollectionResolveContext` implementations.

Apply this shared behaviour only to those file collections that need to resolve arbitrary user provided paths, and simplify the contract for `FileCollectionResolveContext`.

    • -173
    • +8
  1. … 19 more files in changeset.
Consistently show file changes for single root file in Gradle Enterprise (#7422)

* Snapshot SingletonFileTree as RegularFileSnapshot

- extract SingletonFileTree as interface

- rename SingletonFileTree to DefaultSingletonFileTree

- rename MapFileTree to GeneratedSingletonFileTree

- GeneratedSingletonFileTree only accepts one file (as its only used for one file so far)

- add coverage for archives

    • -3
    • +3
  1. … 22 more files in changeset.
Move file collection APIs out of core (#6525)

This change breaks out code that directly relates to handling `FileCollection`s and their build dependencies (called `TaskDependency` at this time) into a separate subproject (`:files`). This is so that other modules can build on just this module instead of having to depend on the oversized `:core`.

As part of the change `Provider`s have been moved to `:base-services`. In a possible followup step `:base-services` could be split into a module that captures the very basic concepts of Gradle's data model: it's all about `DomainObjectCollection`s that can be configured via `Action`s, transformed via `Transformer`s, lazyness can be provided via `Provider`s and rich mutable data types can be created via `Property` objects.

Another addition to `:base-serivces` is the directed graph traversal algorithms used in many parts of Gradle.

    • -0
    • +464
  1. … 443 more files in changeset.