You could try changing the repository location property on the command line to a fresh empty directory. That will force the download and logging of all SNAPSHOT and release dependencies. >mvn ... -Dmaven.repo.local=<new-temp-directory>
<!-- Frank Gorham-Engard → "Be kinder than necessary. Everyone is fighting some kind of battle." -----Original Message----- From: Shan Syed [mailto:shan...@gmail.com] Sent: Friday, July 30, 2010 2:21 PM To: Maven Users List Subject: Re: force maven to redownload/refresh "released" dependencies ok, thanks basically for liability reasons for a certain project, we have to provide specific times of when a project was built and when/where all its dependencies were retrieved at/from we have to ensure a sanitary build for all these JARs and a complete log of going from 0 to 100 for the build; so we are faced with either clearing out the .m2 each time I was wondering if there was a way to force this through maven On Fri, Jul 30, 2010 at 12:57 PM, Manos Batsis <manos_li...@geekologue.com>wrote: > On 07/30/2010 07:16 PM, Wayne Fay wrote: > >> is there a way to force a project to refresh certain dependencies every >>> build? i.e. replicate SNAPSHOT behaviour with "released" artifacts >>> >> >> Absolutely not. Released artifacts MUST NOT CHANGE. >> > > +1, never ever ;-) > > Released artifact versioning is supposed to guarantee consistency. > > Manos > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
