Gradle / subprojects / core / src / integTest / groovy / org / gradle / api / file

FileCollectionIntegrationTest.groovy

Clone Tools

Stats

Commits this week: 0
Total Committers: 4
Last Commit: 16 Jun
Commits this week: 0

Lines of code count not available

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few seconds ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Sunday 16 Jun
2:25 am

Adam Murdoch

int tests for previous commit.

Options
    • -38
    • +0
    ./FileCollectionIntegrationTest.groovy
  2. … 1 more file in changeset.
2:16 am

Adam Murdoch

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.

Options
    • -38
    • +0
    ./FileCollectionIntegrationTest.groovy
  2. … 4 more files in changeset.
2:16 am

Adam Murdoch

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.

Options
    • -38
    • +0
    ./FileCollectionIntegrationTest.groovy
  2. … 4 more files in changeset.
2:16 am

Adam Murdoch

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.

Options
    • -38
    • +0
    ./FileCollectionIntegrationTest.groovy
  2. … 4 more files in changeset.
2:16 am

Adam Murdoch

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.

Options
    • -38
    • +0
    ./FileCollectionIntegrationTest.groovy
  2. … 4 more files in changeset.
2:16 am

Adam Murdoch

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.

Options
    • -38
    • +0
    ./FileCollectionIntegrationTest.groovy
  2. … 4 more files in changeset.
2:16 am

Adam Murdoch

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.

Options
    • -38
    • +0
    ./FileCollectionIntegrationTest.groovy
  2. … 4 more files in changeset.
Monday 13 Aug 2018
9:44 am

Stefan Wolf

Remove FileCollection.add

#6273

Options
    • -26
    • +0
    ./FileCollectionIntegrationTest.groovy
  2. … 6 more files in changeset.
9:30 am

Stefan Wolf

Remove AbstractFileCollection.getBuildDependencies()

#6271

Options
    • -17
    • +0
    ./FileCollectionIntegrationTest.groovy
  2. … 1 more file in changeset.
9:11 am

Stefan Wolf

Remove FileCollection.asType()

#6270

Options
    • -49
    • +0
    ./FileCollectionIntegrationTest.groovy
  2. … 4 more files in changeset.
7:14 am

Stefan Wolf

Remove FileCollection.stopExecutionIfEmpty()

#6269

Options
    • -13
    • +0
    ./FileCollectionIntegrationTest.groovy
  2. … 5 more files in changeset.
Friday 20 Jul 2018
3:56 am

René Gröschke

Deprecation progress events are enriched to allow better visualisation (#6034)

Update deprecation model; tweak deprecation messages

* some renamings in feature usage

* introduce feature usage type

* introduce contextual advice for deprecation messages

Options
    • -1
    • +1
    ./FileCollectionIntegrationTest.groovy
  2. … 28 more files in changeset.
Friday 13 Jul 2018
9:08 am

René Gröschke

Expose deprecation warning messages and stacktraces via build operations (#5881)

Expose deprecation warnings as operation progress events

- introduce split of message, warning and advice

- make deprecation progress events immutable

- rework deprecation handling/messages to support more a richer model

- update build operation progress model

- tweak existing deprecation warnings to match new model

- Add performance test + make stacktrace calculation for build ops lazy

- Always include a trace with FeatureUsage now that its always required

Options
    • -5
    • +5
    ./FileCollectionIntegrationTest.groovy
  2. … 65 more files in changeset.
Wednesday 16 May 2018
3:02 am

Stefan Wolf

Include class name in deprecation message

If not, it is not clear that a third party plugin extended

AbstractFileCollection and it looks like it is a problem with

Gradle core.

Options
    • -1
    • +1
    ./FileCollectionIntegrationTest.groovy
  2. … 1 more file in changeset.
Thursday 05 Apr 2018
6:56 am

Lóránt Pintér

Better deprecation message

Options
    • -0
    • +17
    ./FileCollectionIntegrationTest.groovy
  2. … 1 more file in changeset.
Wednesday 28 Mar 2018
7:20 am

Lóránt Pintér

Fix incorrect type name

Options
    • -1
    • +1
    ./FileCollectionIntegrationTest.groovy
  2. … 1 more file in changeset.
6:42 am

Lóránt Pintér

Integrate review feedback

Options
    • -0
    • +26
    ./FileCollectionIntegrationTest.groovy
  2. … 5 more files in changeset.
5:02 am

Lóránt Pintér

Deprecate FileCollection.stopExecutionIfEmpty()

Options
    • -0
    • +13
    ./FileCollectionIntegrationTest.groovy
  2. … 3 more files in changeset.
Thursday 22 Mar 2018
8:39 am

Lóránt Pintér

Deprecate FileCollection.asType()

The method was used to add some special conversions for `FileCollection` in Groovy. In an attempt to remove Groovy-specific functionality from public API the method is now deprecated. The type conversions, while not widely used to start with, will mostly keep working because `FileCollection` implements `Iterable<File>` which Groovy know how to convert to other collections.

Options
    • -0
    • +87
    ./FileCollectionIntegrationTest.groovy
  2. … 4 more files in changeset.