Hi, I have a few coming from p2 plugins and .lock/.part files (missing cleanup but no big deal I guess). All other 0 sized artifacts are related to data exploded in .m2 by plugins but unrelated to maven (like graal distro exploded, npm tar.gz exploded etc).
Side note: I mainly use 3.6.3 on projects so can be in a luck case too. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mer. 1 déc. 2021 à 12:23, Slawomir Jaranowski <s.jaranow...@gmail.com> a écrit : > Hi, > > From time to time I have jars in .m2/repository of size 0. > > Probably some network issues are the reason for this situation. > > I can't reproduce this today. > I need some hints which component is responsible for storing artifacts in > .m2 > Or some other hints which can help to reproduce, debug such a situation. > > Does anybody else have a similar problem? > > Please try on your system: > find ~/.m2/repository -type f -size 0 > > I use Maven 3.8.4 > > -- > Sławomir Jaranowski > > https://twitter.com/SlawekJaran > https://github.com/slawekjaranowski > https://linkedin.com/in/slawomirjaranowski >
