So far, you'd end up with as many copies of artifacts as many local repositories you have (I like to keep things separate). Second, in local repository remote artifacts are _mixed_ with locally built ones, and may be even replaced (ie. you check out a project tag and do mvn install w/ soma change)
OK... this makes more sense :D I do only one local repository (.m2) and only use that... when I work on something and publish to local repo (intentionally, to test with other module) then I do _want_ to have it there... :)
There is still the "local repo hygiene"... so you get a coffee when you nuke your local repository? As this is the main goal: when you throw away you local repo, w/ mimir it is "still there" and builds are still fast: https://cstamas.org/blog/2025/01/do-nuke-your-local-repository/
I don't nuke it nor had the need to do it, especially regularly... I sometimes (once a year? every 2 years) do some cleanup/nuke as there may be old/stale artifacts but that's about it. I have never had a situation where I would had to nuke it because of some artifacts going bad...
And in that case I'd say that force-update (single) artifact is still a better option :) besides, with breadth-first dependencyCollector the download is really fast, especially on multi-module project :)
w/ system-wide cache, you have ONE artifact copy on your system as rest are hardlinked from Mimir local cache. Moreover, "nuking local repo" is part of (currently) of repo "hygiene" exactly due it's mixed nature, and is especially painful if you work on multiple branches of several inter-dep prjs
This basically helps you to simply nuke your local repo, even daily, but NOT lose anything (time) with "downloading the internet", as it is already there (mimir today caches Central ONLY, will be improving on that front).
I have a desktop (Linux) and two laptops (Linux and macOS) I use interchangeably, and I _hate_ when I move from one to another to "pick up" all the deps" of project am currently in. With Mimir, I get "shared" cache with laptop on LAN speeds and is almost as fast as doing git update and just continue
Comments
so there is no duplication in my case :)
I get that it _may_ be useful solution, but it seems it's not for me and my use-case made me fail and appreciate it :)