We use maven and continuous integration and it works very very well. SNAPSHOTS are a godsend when it comes to being flexible and delivering something quickly and tested quickly.
We commit many times a day and it is unphathomable to create a concrete release for each of those commits. It would waste a lot of time and resources. When working with SNAPSHOTS you don't worry about "what released version was that problem found on?" You just simply say the error occurs on the trunk and fix it there. The trick here is to have fast feedback. So if you introduce an error today, you should know about that error today or at the latest tomorrow. So you don't have days or weeks go by before you get that feedback. My general advice for devs who get into the rut like the one on the google thread is to switch to concrete releases once you start approaching your release date. So lets say iterations 1 to 10 are on snapshots. Your product owner then feels that you have enough content to ship a release. Create a branch, cut a formal release and have your testing team test that release and iteration 11 with a release. You may have a couple of fixes to do on that branch and you may need to cut a new release to test what you fixed. The idea here though is that 99% of all the feature and bugs were tested and ironed out on SNAPSHOT builds. You just do your last iteration on formal releases. You wait as long as you can before before you move to concrete releases so you don't have to manage multiple branches and tags and all the complication that comes with formal releases. The version numbering would go something like this: 1.0-SNAPSHOT 1.0-SNAPSHOT 1.0-SNAPSHOT 1.0-SNAPSHOT 1.0-SNAPSHOT ... 1.0-01 1.0-02 1.0-03 You release to the field with 1.0-03. > -----Original Message----- > From: stug23 [mailto:[email protected]] > Sent: Monday, November 01, 2010 1:14 PM > To: [email protected] > Subject: Continuous Delivery and Maven > > > I've been reading about Continuous Delivery > <http://continuousdelivery.com/> > and trying to understand how to best combine Maven and Continuous > Delivery. > There is a thread in the Continuous Delivery google group where this > discussion has started: > > <http://groups.google.com/group/continuousdelivery/browse_thread/thread/c > 8440681058f2db8> > > I would be curious as to whether there are other Maven developers > following > the Maven Users forum that have been looking Continuous Delivery and > trying > to grapple with the best way to use Maven in this approach. > -- > View this message in context: > http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven- > tp3245370p3245370.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
