Interesting, we use it in Nexus as a proxy repo and you were right, these
zero-size jars were present in our cache as well.
How did you cleaned-up the cache? Search on filesystem and remove files
with this attributes and updated index within nexus afterwards?
Your help is much appreciated
--
Fra
Hi folks,
I recently stumble about this problem to and my investigation is as follows:
* you a company uses a repository manager and has osger repo as a proxy
repo configured AND
* and internal artefact has been request but is not avaliable in internal
repositories, that a http get is set to osge
