you should group your project into logical modules and release the groups as often as you like, however i dont think it is wise to let everyone do the release at will, there should be a release manager to do that job. Take a look at maven continuum 1.1 which can automate the release job for you in a control manner.
also take a look at maven itself which has multiple project groups ( ie , plexus core, plexus-utils, plexus archiver, doxia, scm, maven etc) hope it helps. -D On 8/27/07, Hilco Wijbenga <[EMAIL PROTECTED]> wrote: > On 8/27/07, Dan Tran <[EMAIL PROTECTED]> wrote: > > you should use maven-release-plugin to do the deployment. This plugin > > always increment the release version after it releases the artitfacts. > > I will definitely take advantage of maven-release-plugin. So far I've > been using "mvn deploy" as these are just tiny modules (and I'm just > trying things). I have also assumed that in a more Agile environment > everybody should be able to do releases of these modules (not of the > entire app). > > Do you think releasing (even of underlying modules) should always be > done by a select few? > > We're just starting on the road to Maven bliss so I'm trying to figure > out what countless people have already mastered. :-) I've been looking > for the philosophy behind Maven releases but I haven't found much. > > --------------------------------------------------------------------- > 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]
