SNAPSHOTs can be effectively considered "nightly builds" of artifacts in many cases. You don't necessarily want to upgrade from a stable 1.4.2 release to an unstable 1.5.0-prealpha on code you depend on in your project, do you?
If you add SNAPSHOTs and don't lock down versions of dependencies in your poms, you will automatically find the most recent code added to your project. Especially on corporate projects, people need a repeatable build process and reliable builds including known artifacts, people do not want to use SNAPSHOTs. So it is entirely up to you on adding SNAPSHOT repos or not. On the same token, someone might want to use only released versions of artifacts but not mind using SNAPSHOTs of Maven plugins, or vice versa. So they will add the Snapshot plugin-repo and allow Maven to automatically upgrade plugins etc but only the Releases repo for other artifacts. Again, this depends on your needs and how you want to set it up. No one can tell you how to set this up, you have to make those decisions for yourself depending on your build process and corporate requirements etc. Wayne On 5/25/06, Adam Hardy <[EMAIL PROTECTED]> wrote:
I would like to avoid as many surprises in future with maven's repositories so I need to figure out how and why a couple of things in maven work. For instance, why is there the seperation between plugin-repositories and straight repositories? Also, why the seperation of snapshots into their own repository? Without knowing the answers to those questions, I am wondering how to configure maven-proxy appropriately. Should I make maven-proxy proxy all the repositories? Both release and snapshot repos? And is it a good idea to configure a couple of the ibiblio mirrors into maven-proxy as well, to minimise effects when ibiblio goes down? Thanks Adam
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
