A toolchain for Minecraft: Java Edition that builds a workspace to interact with the game using the official mappings provided to the public by Mojang Studios.
MIT License
89
stars
18
forks
source link
Return to using a shared cache for remapped jars #24
Due to issues with multi-module projects trying to access the same files concurrently we currently use project-local storage for jars. This is disk-space and performance inefficient, so we should avoid doing it (unless required for situations needing, for example, access-widened jars.
To be able to use a shared cache, we need to:
[ ] Handle locking files being processed
[ ] Implement our own up-to-date checks for gradle
[ ] Make sure caches are versioned to allow using multiple versions of VanillaGradle on the same system
Due to issues with multi-module projects trying to access the same files concurrently we currently use project-local storage for jars. This is disk-space and performance inefficient, so we should avoid doing it (unless required for situations needing, for example, access-widened jars.
To be able to use a shared cache, we need to: