Skip to content

v0.10.0: Xcode, JVM, and Apple dependency caches

Choose a tag to compare

@github-actions github-actions released this 13 Nov 14:00
· 14 commits to main since this release

Xcode, JVM, and Apple dependency caches

Five new providers move the folders that grow fastest on a Mac that builds
for Apple platforms and runs JVM builds.

Provider What moves
Xcode DerivedData, Archives, iOS/watchOS/tvOS/visionOS Device Support, Previews, and the Xcode app cache
Maven repository/
Gradle caches/ and wrapper/dists/
CocoaPods The pod cache and the spec repos
SwiftPM The package cache

Every row moves by symbolic link, so the tool keeps its path.

exodrive check
exodrive migrate --target=/Volumes/External/exodrive --tools=xcode,gradle

The window rail gains an Apple group and a JVM group.

What stays on this Mac

Exodrive does not move ~/Library/Developer/CoreSimulator/Devices. A link
there stops Xcode from creating simulator devices. It also breaks the Files app
inside the simulator.

The simulator folder stays in the list with the state Cannot move and the
reason. You decide what to delete in Xcode.

Exodrive also never moves ~/Library/Developer/Xcode/UserData or
UserData/IB Support. Asset catalog builds write there.

One guard for a Java tool

The process lock now reads a Java main class. The Gradle daemon runs as
org.gradle.launcher.daemon.bootstrap.GradleDaemon, so gradle --stop clears
the lock.

Evidence

This release passed these checks on macOS 26:

  • The full suite with the race detector, go vet, gofmt, golangci-lint,
    and the site check. Windows and Linux cross-compile.
  • A test home with every new folder: 14 moves, then exodrive verify --all
    reported 14 ok. One changed byte reported changed and exit code 1.
    14 rollbacks left an empty ledger and restored every file.
  • A real move on this Mac: ~/.gradle/wrapper/dists (652.1 MB, 22,429 files)
    and ~/.cocoapods/repos (2.5 MB, 1,744 files). The check reported ok for
    both. Both rollbacks restored the folders and emptied the ledger.

Xcode reads the moved folders through the links. This machine holds no Xcode
build output, so a live Xcode build through a link is not proven.

Also

  • README.md, README.zh.md, SPEC.md, and both docs pages describe the five
    providers and the blocked simulator folder.
  • A custom Derived Data location is not read. A cache at that location stays
    out of the list.