[{"data":1,"prerenderedAt":350},["ShallowReactive",2],{"blog-article-\u002Ftw\u002Fblog\u002Fclear-gradle-cache":3},{"id":4,"title":5,"author":6,"body":7,"category":330,"cover":331,"coverAlt":332,"description":333,"draft":334,"extension":335,"meta":336,"navigation":337,"path":338,"publishedAt":339,"seo":340,"stem":341,"tags":342,"topics":346,"translationKey":348,"updatedAt":339,"__hash__":349},"articles_tw\u002Ftw\u002Fblog\u002Fclear-gradle-cache.md","Gradle 快取占用太大，怎麼清理？","Harry",{"type":8,"value":9,"toc":322},"minimark",[10,19,29,32,37,46,49,60,63,76,88,117,121,124,177,191,210,224,228,251,264,275,279,282,285,293,299,306],[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},"\u002Ftw\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",1171,"lazy","https:\u002F\u002Fassets.mangodisk.app\u002Fimages\u002Fscreenshots\u002Fwindows\u002Ftw\u002Flight-01-deep-cleanup.jpg",1746,[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},"\u002Ftw\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,94,220,223],{},"專案裡的 ",[15,214,215],{},"gradle"," 資料夾又是另一回事，通常存放 Wrapper 檔案。它和專案根目錄中的 ",[15,218,219],{},"gradlew",[15,221,222],{},"gradlew.bat"," 都應該保留。",[33,225,227],{"id":226},"為什麼執行-clean空間還是沒變多","為什麼執行 clean，空間還是沒變多",[11,229,230,233,234,237,238,241,242,245,246,87],{},[15,231,232],{},"gradlew clean"," 通常清理的是目前專案的 ",[15,235,236],{},"build"," 輸出，不是使用者目錄下的全域相依套件快取。因此，專案清理成功，",[15,239,240],{},".gradle\u002Fcaches"," 卻還是很大，並不矛盾。自訂的 ",[15,243,244],{},"clean"," 工作可能有額外操作，執行前仍要確認定義。詳細行為可參考 ",[41,247,250],{"href":248,"rel":249},"https:\u002F\u002Fdocs.gradle.org\u002Fcurrent\u002Fuserguide\u002Fcommand_line_interface.html#cleaning_outputs",[188],"Gradle 的 clean 說明",[11,252,253,254,256,257,259,260,263],{},"如果占空間的是舊專案產生的檔案，MangoDisk 的「專案建置產物」可以辨識支援的 Gradle 專案中的 ",[15,255,236],{}," 和專案層級 ",[15,258,17],{},"，讓你按專案檢查後清理。",[22,261,262],{},"這和「Gradle 建置快取」是兩類結果，不是刪除整個專案。"," 若曾把要留存的安裝檔或報告放在這些輸出目錄裡，先複製出來。",[11,265,266,269,270,87],{},[15,267,268],{},"--refresh-dependencies"," 也不是釋放空間的指令。它會重新檢查相依套件，已下載的檔案有效時仍可能沿用，不會清空整個快取。可參考 ",[41,271,274],{"href":272,"rel":273},"https:\u002F\u002Fdocs.gradle.org\u002Fcurrent\u002Fuserguide\u002Fdependency_caching.html#sec:refreshing-dependencies",[188],"Gradle 官方相依套件快取說明",[33,276,278],{"id":277},"清理前想想下次建置需要什麼","清理前，想想下次建置需要什麼",[11,280,281],{},"刪除快取後，下次建置可能比較慢，也可能需要連網下載。如果準備離線工作，或專案使用的套件已無法從公司、舊版套件來源取得，先保留相關快取。",[11,283,284],{},"Gradle 本身有自動清理機制，不必每次建置完都清一次。手動整理比較適合磁碟空間不足、某些專案已經很久沒用，或已確認不再需要某批快取的時候。",[11,286,287,288,292],{},"Gradle 清完仍不夠，可以用 MangoDisk 的",[41,289,291],{"href":290},"\u002Ftw\u002Fdocs\u002Ffeatures\u002Fdisk-analysis","磁碟空間分析","查看整顆磁碟或專案資料夾。沿著較大的方塊逐層打開，看看是不是舊專案、安裝檔，或其他工具的資料還在占空間。",[11,294,295],{},[52,296],{"alt":297,"decoding":55,"height":56,"loading":57,"src":298,"width":59},"MangoDisk 磁碟空間分析，以矩形圖查看資料夾與檔案占用","https:\u002F\u002Fassets.mangodisk.app\u002Fimages\u002Fscreenshots\u002Fwindows\u002Ftw\u002Flight-05-disk-space-analysis.jpg",[11,300,301,305],{},[41,302,304],{"href":303},"\u002Ftw","下載 MangoDisk","，集中檢查分散的開發工具快取和建置產物，再決定哪些值得清理。支援 Windows 和 macOS，免費開源，不必註冊或登入。",[11,307,308,309,313,314,313,318],{},"延伸閱讀：",[41,310,312],{"href":311},"\u002Ftw\u002Fblog\u002Fclear-pnpm-store-cache","pnpm 快取清理"," · ",[41,315,317],{"href":316},"\u002Ftw\u002Fblog\u002Fcargo-cache-vs-target-folder","Cargo 快取與 target 資料夾",[41,319,321],{"href":320},"\u002Ftw\u002Fblog\u002Ftopics\u002Fdeveloper-cleanup","開發者磁碟清理指南",{"title":323,"searchDepth":324,"depth":324,"links":325},"",2,[326,327,328,329],{"id":35,"depth":324,"text":36},{"id":119,"depth":324,"text":120},{"id":226,"depth":324,"text":227},{"id":277,"depth":324,"text":278},"開發者磁碟清理","\u002Fimages\u002Fblog\u002Fclear-gradle-cache.webp","深青色小象旁的橘色刷子掃走灰色快取方塊，保留另一側的專案資料夾","Gradle 快取占了太多空間？用 MangoDisk 查看 Windows 和 Mac 上的開發工具快取與建置產物，確認大小和路徑後再清理，保留原始碼與重要設定。",false,"md",{},true,"\u002Ftw\u002Fblog\u002Fclear-gradle-cache","2026-10-03T10:20:00+08:00",{"title":5,"description":333},"tw\u002Fblog\u002Fclear-gradle-cache",[343,344,345],"Gradle 快取清理","Android Studio","專案建置產物",[347],"developer-cleanup","article-clear-gradle-cache","vYoRQuUo52ZrStWmOSnJ2W0_CcMUmY4q3iPXCl3APNQ",1790994574388]