How would this be different in your old ant builds? I presume that when you shipped to a customer you used a concrete version. Thus you must of worried about concrete versions at some point.
I would say worry about versions at the same point in your maven builds as you did in your old ant builds. You don't need to be constantly cutting a new Maven release during your development cycle. Stay with SNAPSHOTs until you get closer to release. BTW. Be careful with you version numbering here. I believe Maven would flag a version of 1.0.1 as more recent than 1.0-SNAPSHOT. However, if you used 1.0-01, 1.0-SNAPSHOT is considered more recent. Not overly serious but something to be aware of. --- Todd Thiessen > -----Original Message----- > From: slanted [mailto:[email protected]] > Sent: Tuesday, November 10, 2009 12:59 PM > To: [email protected] > Subject: development methodology > > > Our development team recently mavenized a couple of our web > applications. We are struggling a bit with the new > development methodology. > > A brief description of our artifacts and our setup: > > We have 2 web applications: shop & signup. > These 2 web applications are both dependant on 2 jars: > content.jar & libs.jar. > We use IntelliJ for our IDE and Hudson for a CI/build server. > > Now for our 'process': > > - Suppose we add some new functionality to our libs.jar. > We increment the > version, let's say from 1.0.0 to 1.0.1. > - Now we release libs version 1.0.1 > - Now we update the shop & signup web apps to be > dependant on libs 1.0.1. > And we release both of them > - Now QA finds a bug in the libs. > - Change the libs.jar pom to be 1.0-SNAPSHOT, indicating > development. > - The developers change shop & signup poms to be dependant on libs > 1.0-SNAPSHOT > - Develop the fix > - Now we increment libs.jar to version 1.0.2 > - Update shop & signup web apps to be dependant on 1.0.2. Release. > - Another bug is found... > - Change the libs.jar pom to be 1.0-SNAPSHOT, indicating > development > - The developers change shop & signup poms to be dependant on libs > 1.0-SNAPSHOT > - Develop the fix... > - And so on > > Now for the question: For a simple setup like this, is Maven overkill? > > Our development process was quite a bit simpler when we were > using ANT and didn't worry about the versions. > > Before, everyone just updated from subversion and got the > latest code and there was no worrying about updating our pom > files with each test/release cycle. > > We've gone the maven route and would like to stick with it. > Could anyone comment on our process and maybe point out some > ways to improve this constant pom updating? > > Thanks, > Eric > > -- > View this message in context: > http://old.nabble.com/development-methodology-tp26287355p26287355.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]
