[{"data":1,"prerenderedAt":355},["ShallowReactive",2],{"blog-article-\u002Fzh\u002Fblog\u002Fclear-gradle-cache":3},{"id":4,"title":5,"author":6,"body":7,"category":335,"cover":336,"coverAlt":337,"description":338,"draft":339,"extension":340,"meta":341,"navigation":342,"path":343,"publishedAt":344,"seo":345,"stem":346,"tags":347,"topics":351,"translationKey":353,"updatedAt":344,"__hash__":354},"articles_zh\u002Fzh\u002Fblog\u002Fclear-gradle-cache.md","Gradle 缓存太大了，怎么清理？","Harry",{"type":8,"value":9,"toc":327},"minimark",[10,19,29,32,37,46,49,60,63,76,88,117,121,124,177,191,210,227,231,254,267,278,282,285,288,296,304,311],[11,12,13,14,18],"p",{},"项目已经不做了，Gradle 下载的依赖和构建时生成的缓存，却可能还留在电脑上。用 Android Studio、IntelliJ IDEA 做过几个项目后，用户目录里的 ",[15,16,17],"code",{},".gradle"," 就值得检查一下。",[11,20,21,28],{},[22,23,24,25,27],"strong",{},"Gradle 缓存可以清理，但别把整个 ",[15,26,17],{}," 文件夹直接删掉。"," 里面除了缓存，还有可能存着全局配置。清理后，后续构建可能需要重新下载依赖、重新生成文件；正在用的项目，尤其是离线项目，不必为了腾空间全部清空。",[11,30,31],{},"不想挨个找目录，可以先用 MangoDisk 看看 Gradle 和其他开发工具分别占了多少空间，再决定清哪一项。",[33,34,36],"h2",{"id":35},"用-mangodisk-找出值得清理的缓存","用 MangoDisk 找出值得清理的缓存",[11,38,39,40,45],{},"打开 MangoDisk 的",[41,42,44],"a",{"href":43},"\u002Fzh\u002Fdocs\u002Ffeatures\u002Fdeep-clean","深度清理","，扫描后在「开发工具」中查看「Gradle 构建缓存」。展开结果，就能核对占用大小和实际路径，不用先记住那些隐藏目录在哪里。",[11,47,48],{},"同一个页面也能比较 npm、pnpm、Cargo 等受支持的开发缓存。磁盘快满时，先处理占用大、清理后也能重新获取的内容，比把所有缓存一口气删掉更实用。",[11,50,51],{},[52,53],"img",{"alt":54,"decoding":55,"height":56,"loading":57,"src":58,"width":59},"MangoDisk 深度清理，集中查看开发工具缓存的大小","async",1233,"lazy","https:\u002F\u002Fassets.mangodisk.app\u002Fimages\u002Fscreenshots\u002Fwindows\u002Fzh\u002Flight-01-deep-cleanup.jpg",1838,[11,61,62],{},"准备清理 Gradle 时：",[64,65,66,70,73],"ol",{},[67,68,69],"li",{},"保存工作，结束构建和同步，退出 Android Studio、IntelliJ IDEA 等相关程序，并按提示关闭 Gradle、Java 进程。",[67,71,72],{},"取消不准备清理的项目，只勾选已经检查过的 Gradle 缓存。",[67,74,75],{},"核对所选路径和清理影响，再确认执行。扫描本身不会删除文件。",[11,77,78,79,82,83,87],{},"MangoDisk 清理的是选中范围内的缓存，不会替你判断哪些依赖以后还会用到。",[22,80,81],{},"删除不经过回收站；需要保留的离线依赖或无法重新获取的文件，先备份。"," 恢复限制见",[41,84,86],{"href":85},"\u002Fzh\u002Fdocs\u002Fsafety","安全清理指南","。",[11,89,90,91,94,95,94,98,101,102,105,106,109,110,94,113,116],{},"Windows 上的 Gradle 清理范围包括 ",[15,92,93],{},"caches","、",[15,96,97],{},"daemon",[15,99,100],{},"workers"," 和 ",[15,103,104],{},"notifications","；macOS 还包括下载的 Gradle Wrapper 发行包和 ",[15,107,108],{},".tmp"," 临时目录。项目源码、全局 ",[15,111,112],{},"gradle.properties",[15,114,115],{},"init.d"," 脚本和 JDK 不在这条缓存规则的清理范围内。",[33,118,120],{"id":119},"手动清理时别删错文件夹","手动清理时，别删错文件夹",[11,122,123],{},"Gradle 默认把用户级数据放在这些位置：",[125,126,127,143],"table",{},[128,129,130],"thead",{},[131,132,133,137,140],"tr",{},[134,135,136],"th",{},"系统",[134,138,139],{},"默认目录",[134,141,142],{},"打开方式",[144,145,146,160],"tbody",{},[131,147,148,152,157],{},[149,150,151],"td",{},"Windows",[149,153,154],{},[15,155,156],{},"%USERPROFILE%\\.gradle",[149,158,159],{},"粘贴到文件资源管理器的地址栏",[131,161,162,165,170],{},[149,163,164],{},"macOS",[149,166,167],{},[15,168,169],{},"~\u002F.gradle",[149,171,172,173,176],{},"Finder 中按 ",[15,174,175],{},"Shift + Command + G","，粘贴路径",[11,178,179,180,183,184,190],{},"如果配置过 ",[15,181,182],{},"GRADLE_USER_HOME","，以实际设置的目录为准。MangoDisk 的标准 Gradle 规则检查默认位置，不保证覆盖你另外指定的目录。",[41,185,189],{"href":186,"rel":187},"https:\u002F\u002Fdocs.gradle.org\u002Fcurrent\u002Fuserguide\u002Fdirectory_layout.html",[188],"nofollow","Gradle 官方目录说明","也区分了缓存、配置和下载的工具。",[11,192,193,194,196,197,199,200,202,203,205,206,209],{},"手动处理同样要先关闭相关程序。打开目录后，先查看 ",[15,195,93],{}," 的大小和内容，确认要清理，再删除目标文件夹；不要连同外层 ",[15,198,17],{}," 一起删除。",[15,201,112],{}," 可能保存了代理或仓库设置，",[15,204,115],{}," 可能有团队使用的脚本，",[15,207,208],{},"jdks"," 则是构建要用的 Java 环境。",[11,211,212,213,216,217,219,220,94,223,226],{},"项目里的 ",[15,214,215],{},"gradle"," 文件夹也不是用户目录里的 ",[15,218,17],{}," 缓存。它通常存放 Wrapper 文件，和项目根目录中的 ",[15,221,222],{},"gradlew",[15,224,225],{},"gradlew.bat"," 一样，应当保留。",[33,228,230],{"id":229},"为什么运行-clean空间还是没腾出来","为什么运行 clean，空间还是没腾出来",[11,232,233,236,237,240,241,244,245,248,249,87],{},[15,234,235],{},"gradlew clean"," 通常清理的是当前项目的 ",[15,238,239],{},"build"," 输出，不是用户目录下的全局依赖缓存。所以，项目清理成功了，",[15,242,243],{},".gradle\u002Fcaches"," 仍然很大，并不矛盾。自定义项目的 ",[15,246,247],{},"clean"," 任务可能有额外操作，执行前仍要确认任务定义。具体行为可查 ",[41,250,253],{"href":251,"rel":252},"https:\u002F\u002Fdocs.gradle.org\u002Fcurrent\u002Fuserguide\u002Fcommand_line_interface.html#cleaning_outputs",[188],"Gradle 的 clean 说明",[11,255,256,257,259,260,262,263,266],{},"如果是旧项目里的构建文件占了空间，MangoDisk 的「项目构建产物」可以识别受支持 Gradle 项目中的 ",[15,258,239],{}," 和项目级 ",[15,261,17],{},"，让你按项目核对后清理。",[22,264,265],{},"这与「Gradle 构建缓存」是两类结果，不是删除项目本身。"," 如果曾把需要留存的安装包或报告放进这些输出目录，先复制出来。",[11,268,269,272,273],{},[15,270,271],{},"--refresh-dependencies"," 也不是释放空间的命令。它用于重新检查依赖，已有文件有效时仍可能复用，不会把整个缓存库清空。",[41,274,277],{"href":275,"rel":276},"https:\u002F\u002Fdocs.gradle.org\u002Fcurrent\u002Fuserguide\u002Fdependency_caching.html#sec:refreshing-dependencies",[188],"Gradle 官方依赖缓存说明",[33,279,281],{"id":280},"清理前留意下一次构建","清理前，留意下一次构建",[11,283,284],{},"删除缓存后，下一次构建可能更慢，也可能需要联网下载。准备离线工作，或项目依赖已经无法从公司仓库、旧仓库获取时，先保留相应缓存。",[11,286,287],{},"Gradle 本身有自动清理机制，不需要每次构建后都清一遍。手动整理更适合磁盘空间紧张、长期不用某些项目，或确认某批缓存已经不需要的情况。",[11,289,290,291,295],{},"如果 Gradle 清完了，空间仍然不够，可以用 MangoDisk 的",[41,292,294],{"href":293},"\u002Fzh\u002Fdocs\u002Ffeatures\u002Fdisk-analysis","磁盘空间分析","查看整块盘或项目所在目录。顺着占用较大的方块逐层打开，看看是不是旧项目、安装包或其他工具的数据还在占空间。",[11,297,298],{},[52,299],{"alt":300,"decoding":55,"height":301,"loading":57,"src":302,"width":303},"MangoDisk 磁盘空间分析，用矩形图查看目录和文件占用",1171,"https:\u002F\u002Fassets.mangodisk.app\u002Fimages\u002Fscreenshots\u002Fwindows\u002Fzh\u002Flight-05-disk-space-analysis.jpg",1746,[11,305,306,310],{},[41,307,309],{"href":308},"\u002Fzh","下载 MangoDisk","，把分散的开发缓存和构建产物集中检查，再决定哪些值得清理。支持 Windows 和 macOS，免费开源，无需注册或登录。",[11,312,313,314,318,319,318,323],{},"相关阅读：",[41,315,317],{"href":316},"\u002Fzh\u002Fblog\u002Fclear-pnpm-store-cache","pnpm 缓存清理"," · ",[41,320,322],{"href":321},"\u002Fzh\u002Fblog\u002Fcargo-cache-vs-target-folder","Cargo 缓存与 target 文件夹",[41,324,326],{"href":325},"\u002Fzh\u002Fblog\u002Ftopics\u002Fdeveloper-cleanup","开发者磁盘清理指南",{"title":328,"searchDepth":329,"depth":329,"links":330},"",2,[331,332,333,334],{"id":35,"depth":329,"text":36},{"id":119,"depth":329,"text":120},{"id":229,"depth":329,"text":230},{"id":280,"depth":329,"text":281},"开发者磁盘清理","\u002Fimages\u002Fblog\u002Fclear-gradle-cache.webp","深青色小象旁的橙色刷子清走灰色缓存方块，保留独立的项目文件夹","Gradle 缓存占用太大？用 MangoDisk 查看 Windows 和 Mac 上的开发缓存与项目构建产物，核对大小和路径后按需清理，保留项目源码和重要配置。",false,"md",{},true,"\u002Fzh\u002Fblog\u002Fclear-gradle-cache","2026-10-03T10:20:00+08:00",{"title":5,"description":338},"zh\u002Fblog\u002Fclear-gradle-cache",[348,349,350],"Gradle 缓存清理","Android Studio","项目构建产物",[352],"developer-cleanup","article-clear-gradle-cache","DVCFU0acoXMMUMflcUDnxlcalFwRg3rhE2UpJlaBERk",1790994574360]