groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename FileMetadata{Snapshot -> }

Snapshot doesn't add anything to the name.

  1. … 46 more files in changeset.
Address some review feedback.

  1. … 3 more files in changeset.
Stat named pipes as missing files

as we do when we encounter those types when walking

a directory.

  1. … 4 more files in changeset.
Inline method in test

Add more tests for stating symlinks

Allow stating a symlink cycle

via native platform.

  1. … 1 more file in changeset.
Allow stating a symlink cycle

via native platform.

  1. … 1 more file in changeset.
Allow stating a symlink cycle

via native platform.

  1. … 1 more file in changeset.
Allow stating a symlink cycle

via native platform.

  1. … 1 more file in changeset.
Allow stating a symlink cycle

via native platform.

  1. … 1 more file in changeset.
Detect cycles for symlinks

in `DirectorySnapshotter`.

  1. … 2 more files in changeset.
Detect cycles for symlinks

in `DirectorySnapshotter`.

  1. … 2 more files in changeset.
Determine symlink access in stat

This way we can use the information when deciding what to

watch.

  1. … 9 more files in changeset.
Determine symlink access in stat

This way we can use the information when deciding what to

watch.

  1. … 9 more files in changeset.
Determine symlink access in stat

This way we can use the information when deciding what to

watch.

  1. … 9 more files in changeset.
Add a test for stating symlinks pointing to symlinks

Add a test for stating symlinks pointing to symlinks

Add a test for NativePlatformBackedFileMetadataAccessor

Add a test for NativePlatformBackedFileMetadataAccessor

Rename DefaultFileMetadata{ -> Snapshot}

so it is consistent with the interface.

  1. … 9 more files in changeset.
Rename DefaultFileMetadata{ -> Snapshot}

so it is consistent with the interface.

  1. … 9 more files in changeset.
Fix test on Java 8

Native platform provides a more precise modified

time than Java NIO on Java 8.

Fix test on Java 8

Native platform provides a more precise modified

time than Java NIO on Java 8.

Fix test on Java 8

Native platform provides a more precise modified

time than Java NIO on Java 8.

Fix test on Java 8

Native platform provides a more precise modified

time than Java NIO on Java 8.

Use native platform for stat by default

instead of using Java NIO APIs with a `File.exists()`

on Linux and Windows.

This is a preparation for #12966.

  1. … 4 more files in changeset.
Use native platform for stat by default

instead of using Java NIO APIs with a `File.exists()`

on Linux and Windows.

This is a preparation for #12966.

  1. … 4 more files in changeset.
Remove test precondition: FIX_TO_WORK_ON_JAVA9 (#12940)

Gradle clearly works with Java 9 (and later) by now. There should

be nothing left to be fixed. The remaining usages of this annotation

where wrong:

- The test is not testing a feature of Gradle, but of Java or another

tool that only works with java versions < 9

Replaced precondition with: JDK8_OR_EARLIER

(or JDK9_OR_LATER depending on how it is used)

- Test is running older Gradle versions that do not support Java9+

Replaced precondition with: JDK8_OR_EARLIER

- Test itself was using features of Java not available anymore in Java9+

Removed precondition and fixed test to do the test setup differently.

  1. … 11 more files in changeset.
Remove test precondition: FIX_TO_WORK_ON_JAVA9

Gradle clearly works with Java 9 (and later) by now. There should

be nothing left to be fixed. The remaining usages of this annotation

where wrong:

- The test is not testing a feature of Gradle, but of Java or another

tool that only works with java versions < 9

Replaced precondition with: JDK8_OR_EARLIER

(or JDK9_OR_LATER depending on how it is used)

- Test is running older Gradle versions that do not support Java9+

Replaced precondition with: JDK8_OR_EARLIER

- Test itself was using features of Java not available anymore in Java9+

Removed precondition and fixed test to do the test setup differently.

  1. … 11 more files in changeset.
Remove test precondition: FIX_TO_WORK_ON_JAVA9

Gradle clearly works with Java 9 (and later) by now. There should

be nothing left to be fixed. The remaining usages of this annotation

where wrong:

- The test is not testing a feature of Gradle, but of Java or another

tool that only works with java versions < 9

Replaced precondition with: JDK8_OR_EARLIER

(or JDK9_OR_LATER depending on how it is used)

- Test is running older Gradle versions that do not support Java9+

Replaced precondition with: JDK8_OR_EARLIER

- Test itself was using features of Java not available anymore in Java9+

Removed precondition and fixed test to do the test setup differently.

  1. … 11 more files in changeset.