Replacing a SNAPSHOT with a non-SNAPSHOT version is equivalent to upgrading. Jason is right in that this should never be automatically done by Maven. Maven cannot guess or determine when you are ready to give up SNAPSHOT versions.
However, perhaps you need an external batch process that discovers new versions and automatically upgrades POMs. Paul On Fri, Jul 30, 2010 at 1:21 PM, Shan Syed <shan...@gmail.com> wrote: > 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 > > > > >
