This is one approach I am considering as well. -----Original Message----- From: Michael McCallum [mailto:[EMAIL PROTECTED] Sent: November 6, 2008 5:05 PM To: Maven Users List Subject: Re: Release Management Questions
I would highly recommend you externalise environmental configuration such that you don't need to rebuild any artifacts when moving them from one environment to another. On Fri, 07 Nov 2008 08:46:31 Hayward Lam wrote: > Hi all, > > > > We have in-house maven projects. The build requires environment specific > property replacement (i.e. dev, qa and prod) and we set up profiles for > them. When the project has been tested and is ready for release, we can > deploy the artifacts (dev, qa and prod) to our internal maven > repository. > > > > My questions are: > > 1) Is there some sort of release management tool that can automate > this process? > > 2) We use Hudson for continuous integration. The configuration will > be based on each environment only (i.e. -P env-dev). So, each build will > have its own build number. Is there some consolidated way to do this? > i.e. same build number for dev, qa and prod. > > 3) What is the practice that works for you? > > > > Thanks > > -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __________ Information from ESET Smart Security, version of virus signature database 3592 (20081106) __________ The message was checked by ESET Smart Security. http://www.eset.com __________ Information from ESET Smart Security, version of virus signature database 3594 (20081107) __________ The message was checked by ESET Smart Security. http://www.eset.com
