We have thought about this but since it cannot prevent local snapshots it is not really a solution only a technique to limit the problem. BTW, we use TeamCity for CI, builds get farmed out to many build agents so what is in their local repo is quite random; sometimes it works sometimes it doesn't.
We do keep our snapshots on a separate repo (different server port no less) but again this really doesn't help fix the problem. There is no solution (we can come up with) other than patching maven. I have done this and submitted the patch with my JIRA. Unfortunately, my JIRA got closed in favor of this JIRA w/ patch. But then this discussion started and no fix has been implemented... Michael McCallum-3 wrote: > > another thought... > > by default you could not have snapshot repositories enabled and just > enable > them with a profile... > > that way all builds by default have no snapshots, you could even have > separate > profiles and snapshot repos for different departments to a allow more > flexible integration > -- > Michael McCallum > Enterprise Engineer > mailto:[EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Version-ranges-and-snapshots-tp11464715s177p14748696.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
