You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Storing the Minecraft libraries in the home cache would reduce wait times and disk usage greatly when managing two or more clones of the repository, instead of downloading them on each copy of QM.
The text was updated successfully, but these errors were encountered:
@lukebemish would putting @CachableTask on the task that downloads the libraries achieve basically the same result as putting them in the global .gradle cache?
CacheableTask only matters if build cache is on. If the goal is just not re-downloading anything, you shouldn't have to do anything -- normal old up-to-date checks should be enough. If the goal is sharing between different cloned copies of the repo -- use CacheableTask and enable build cache, yeah. Custom caching in the gradle home directory is very hard to do correctly in a way that doesn't lead to locking issues.
Storing the Minecraft libraries in the home cache would reduce wait times and disk usage greatly when managing two or more clones of the repository, instead of downloading them on each copy of QM.
The text was updated successfully, but these errors were encountered: