I think this is an area where NexusPro or the concept of a staging repository can be helpful. You gladly burn version numbers all through the dev process and at some point promote a version to the staging repo for "blessed" deployment. I am not trying to impose a specific point in the pipeline where this happens, as I think the is organizational. With this model you keep your non-staging repo small by cleaning up old artifacts on a regular schedule.
Essentially you treat the non-staging repo as snapshots within your organization. With in a team I suppose you could continue to use snapshots. Granted this approach would require slight different deployment scrips based on environment, but they could use the same mechanism to deploy which I think is the heart of CD. -- View this message in context: http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3255954.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
