Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Revert "Fetch shallow directory snapshot on missing include file"

In the current state, this is not fast enough.

This reverts commit a3947943

  1. … 4 more files in changeset.
Fetch shallow directory snapshot on missing include file

  1. … 4 more files in changeset.
Revert "Read the full search dir"

This reverts commit fe9cd6d5

Normalize include paths when necessary

  1. … 1 more file in changeset.
Only normalize the includePath for includes

since the prefix is already normalized.

Normalize include paths

Absolute paths which enter the virtual file system need to be

normalized.

  1. … 1 more file in changeset.
Read the full search dir

Instead of checking out the individual files afterwards.

Simplify searching for include file

Replace usages of `getRegularFileContentHash` by VFS

  1. … 6 more files in changeset.
Deincubate the new C++ and Swift plugins

    • -2
    • +0
    ./language/ComponentWithDependencies.java
    • -2
    • +0
    ./language/ComponentWithTargetMachines.java
  1. … 99 more files in changeset.
Mark a task as "did work" even when it only deleted stale outputs

    • -2
    • +2
    ./language/assembler/tasks/Assemble.java
  1. … 13 more files in changeset.
Rename StaleClassCleaner to StaleOutputCleaner and add Javadoc

    • -2
    • +2
    ./language/assembler/tasks/Assemble.java
  1. … 12 more files in changeset.
Simplify StaleClassCleaner API

    • -4
    • +7
    ./language/assembler/tasks/Assemble.java
  1. … 10 more files in changeset.
Make :docs:checkstyleApi happy

Signed-off-by: Paul Merlin <paul@gradle.com>

Remove outdated reference to FileOperations in comments

Signed-off-by: Paul Merlin <paul@gradle.com>

Use Deleter in cleaning stale outputs, take 2

This covers the remaining use cases:

- stale class cleanup for compilers

- stale overlapping output cleanup

    • -1
    • +7
    ./language/assembler/tasks/Assemble.java
  1. … 28 more files in changeset.
Move Deleter interface out of impl package

    • -1
    • +1
    ./language/swift/tasks/SwiftCompile.java
  1. … 41 more files in changeset.
Use Deleter in IncrementalSwiftCompile

    • -3
    • +14
    ./language/swift/tasks/SwiftCompile.java
  1. … 1 more file in changeset.
Remove automatic feature preview activation in CppBasePlugin

This is no longer needed, as publishing Gradle Module Metadata

is now the default behavior.

    • -8
    • +1
    ./language/cpp/plugins/CppBasePlugin.java
Move UnexportMainSymbol task to nativeplatform

This task is now shared between C++ and Swift, the package should

reflect that.

    • -141
    • +0
    ./language/swift/tasks/UnexportMainSymbol.java
  1. … 2 more files in changeset.
Unexport wmain/_wmain on Windows

For gradle-native Issue gradle/gradle-native#277

It is possible for windows application to use wmain/_wmain as their entrypoint

rather than main/main.

https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-6.0/aa299386(v=vs.60)

These entrypoints must also be unexported when linking executable object files

to the cpp-unit executable.

Signed-off-by: nigelgbanks <nigel.g.banks@gmail.com>

    • -0
    • +2
    ./language/swift/tasks/UnexportMainSymbol.java
Specialize getBinaries from XCTest components

  1. … 4 more files in changeset.
Remove dependency on HashCode in HashUtil

  1. … 5 more files in changeset.
Wrap the patternSet

Instead of using a strategy.

  1. … 35 more files in changeset.
Do not use PatternSet in snapshots package

Use a pluggable type instead.

  1. … 41 more files in changeset.
Change ArrayLists, used as Queues to ArrayDeques and LinkedLists

removing the first element is linear in an ArrayList

  1. … 9 more files in changeset.
Add missing @Override to all modules

Signed-off-by: Paul Merlin <paul@gradle.com>

  1. … 994 more files in changeset.
Fix checkstyle issues

  1. … 6 more files in changeset.
Use the `DomainObjectCollectionFactory` everywhere

  1. … 36 more files in changeset.
Added `getLocationOnly()` to file system properties, to provide lazy access to just the location of the file system element, rather than both the location and the content of the file system element.

This can be used when mapping the location of a task output to produce an input to some other task, without implying a dependency on the producing task. For example, an IDE project file generation task may need to know where some output will end up (so need to know its location) but does not use the content of the output.

    • -11
    • +1
    ./language/plugins/NativeBasePlugin.java
  1. … 9 more files in changeset.