Well, for example, we don't release automatically. We launch manually it via a special release plugin through hudson, itself launching a maven release through the maven-release-plugin.
This makes it easier to keep a clean release environment. Releasing from a development machine would add risk since it (1) might be less close to the production system and (2) might contain things depending on the dev box that wasn't added to the SCM. Snapshot builds are totally sufficient for us to handle testing purposes. Cheers 2010/9/15 baz themail <[email protected]> > Hi, > > I have been searching the maven website and articles but not sure if i > get the best practice for managing snapshots and release. > Specifically, if continuous builds produce maven snapshot builds, then > when will i produce maven release builds using maven release plug-in? > > Will I ever produce a maven release build via an automated build job > that runs daily for example? The problem with that is: Because maven > plugin is incrementing pom.xml, and the automated build job will > always detect changes even tho there is no changes in the produce > software code. Does it even make sense? Or, release build should be > run manually depending on the release schedule? > > Thank you. > > A. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
