Thanks for the URL. It looks like something we can use. -----Original Message----- From: Rogier Peters [mailto:[EMAIL PROTECTED] Sent: November 7, 2008 3:14 AM To: Maven Users List Subject: Re: Release Management Questions
Do you know about http://maven.apache.org/plugins/maven-release-plugin/ ? If you need more info I can ping my colleagues who have a similar setup On Thu, Nov 6, 2008 at 8:46 PM, Hayward Lam <[EMAIL PROTECTED]> 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 > > __________ Information from ESET Smart Security, version of virus signature database 3594 (20081107) __________ 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
