Just wanted to quickly chime in with a CI build use case: We use CruiseControl with Distributed extensions, which means a given build may be run any one out of 12 or so machines. In a case where project B depends on project A, this means snapshot project A may build on machine 1, after which snapshot project B builds on machine 2. The snapshot deployed by project A will not be installed locally on machine 2, but will be available in the snapshot repo after project A builds and deploys it's latest snapshot. For this use case, we depend on maven getting the latest deployed snapshots from the snapshot repo every time in order to ensure project B/machine 2 builds with the latest dependencies.
Dan -----Original Message----- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, August 06, 2007 12:25 PM To: Maven Developers List Subject: Re: Making snapshot updates a manual process? ... A CI machine would also benefit from this as everything is being built locally and nothing should be pulled from a remote repository. ... Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com ---------------------------------------------------------- -------------------------------------------------- This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. -------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
