There is a maxim to follow when deploying: "do not redeploy a version more than once". Once you deploy version X.Y.Z, it should never be updated, and those who download it never need to download it again. So, back to the original problem, are you guys doing that?
On Fri, Jul 30, 2010 at 3:57 PM, Shan Syed <shan...@gmail.com> wrote: > it only applies to our final release cuts, not our day-to-day > just once for this project really; I wanted to insert such this switch (if > existed) in our "delivery build" profile > we use archiva for everything else, and actually only make use of public > maven repositories when we up a version of our dependencies, which is rare > because of change control > > it's all weird stuff, I know, but sometimes I just don't question it > > On Fri, Jul 30, 2010 at 4:51 PM, Wayne Fay <wayne...@gmail.com> wrote: > > > >> deleting the m2 works, I was just curious to see if there was a switch > > in > > >> maven to force all downloads again > > > > > > This makes absolutely no sense, doesn't change your BOM, and is just > > > wasteful. Consumes bandwidth unnecessarily from a resource that is > being > > > used by the whole Maven community. > > > > I'd think that if you had enough developers doing this on every > > machine on a consistent basis (eg every build), it might add up to > > enough traffic to get you on a blacklist somewhere... You really need > > to install Nexus or another MRM, this is just plain dumb. > > > > Wayne > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
