Allison, Bob wrote on Saturday, October 29, 2005 2:52 AM: > Jörg Schaible wrote on Friday, October 28, 2005 3:24 PM: >> It would be good to advertise maven-proxy much more. It works >> really fine even for M2. Especially for companies or other >> big organizations it can decrease the traffic significantly. >> >> What's missing: >> A proper guide how to make use of it in M2 (it took me some >> time to get the <home>/.m2/settings.xml right, so that >> artifacts and plugins will use the >> proxy) and special hints in the M2 docs for its existence. > > One problem I have been having with maven-proxy is that I > find that once a jar's metadata is downloaded, it never seems > to be updated. I noticed this when Maven 2.0 was released. > Soon after that, a few plugins had new versions released but > my Maven 2.0 never updated, even using -U and blasting the > repository. Only by stopping the proxy, blasting it's cache, > and restarting it was I able to get the updated plugins. I > think there may need to be a serious code review of this to > make sure that it is working correctly with m2 before it is heavily > advertised.
OK. So can anyone of the Maven devs explain, what files have to be checked remotely so I can create patches for maven-proxy? Are only the metadata*.xml to be checked again or additionally the *.pom files ? - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
