write perms are an assumptions, indeed you can make it optional with a lot of config but not under our radar nor a supported feature IMHO
Romain Manni-Bucau @rmannibucau <https://x.com/rmannibucau> | .NET Blog <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> Javaccino <https://javaccino.dev/> founder (Java/.NET service - contact via linkedin) Le lun. 3 août 2026 à 17:22, Matthias Bünger <[email protected]> a écrit : > > since .m2 already has a ton of living and even temp files (snapshots for > ex > > which are still needed there quite often) then it doesn't hurt as much as > > it can sound to do it there, in particular with split repo it will be > free > > and "by design" > > Are you sure that the Maven process always has deletion rights in .m2, > esp in container environments where .m2 is just injected from outsite to > avoid downloading stuff over (and over and therefore also shared across > multiple). So like having "r-x" on directory, but files have "rw-"? > > >
