I see only one case where it could be useful, it is when we use staging repositories and have to update our released binaries. It is a shame to have to manually remove binaries previously downloaded (and it is error prone). I agree that never updating released binaries is a maven fundamental and we'll never change that. But we'll have to improve tooling around staging to easily allow to cleanup the local repository (or a part of it) for QA teams and others involved in staging process. Cheers,
Arnaud On Jul 30, 2010, at 6:39 PM, Jason van Zyl wrote: > Maven won't do that, and we would never make that possible. If you require > this you have something seriously wrong with your project infrastructure. > Seriously bad project infrastructure smell. > > On Jul 30, 2010, at 12:01 PM, Shan Syed wrote: > >> is there a way to force a project to refresh certain dependencies every >> build? i.e. replicate SNAPSHOT behaviour with "released" artifacts >> >> S > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
