Well I guess you should change the update policy instead. SNAPSHOTs is a crucial concept for us: it allows to continuously integrate our components, test them, etc.
If your build break way,way,way,... to much it might be worse if you disable snapshots resolution. Anyway, update policy is the way to go, IMO. Regards, Stéphane On 8/6/07, Jason Dillon <[EMAIL PROTECTED]> wrote: > Any thoughts on how things might work if the snapshot update bits > where a manual process? So that you have to run mvn with some flag > to pull in new snapshot artifacts, and perhaps another interactive > flag to allow only specific snapshots to be updated (with some > relatively smart warning/suggestion on other snaps to update when one > is selected)? > > I really hate when my build was working fine, I'm testing out new > features I've added to my project then run a build and it pulls down > some new snaps and then hoses my build. This happens *way, way, way* > to much. > > Anyways, was just something I was pondering. I'd really like to `mvn > -up` just like `svn up` to pull in new bits when I'm ready to handle > them. > > --jason > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
