Re: Maven release strategy

2008-02-27 Thread Graham Leggett

Sebastian Johnck wrote:


I am comparing the differences between performing one
release from the top most module, which forces a
release of all child modules, vs releasing one child
module at a time. Which is better?


It depends entirely on your needs.

Releasing modules on their own means that you are releasing "small" 
chunks of code at a time, and in turn, any new problems are probably 
caused by the code you just released. You will end up doing more 
releases though, but in theory this shouldn't be a problem, as the 
release plugin makes it easy.


Sometimes however you might have a situation where a client and server 
must be released together, or when your release contains assemblies, and 
here you are forced to do a multi-module release.


Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature


Maven release strategy

2008-02-27 Thread Sebastian Johnck
I am comparing the differences between performing one
release from the top most module, which forces a
release of all child modules, vs releasing one child
module at a time. Which is better?

Can any one recommend some good documentation on maven
release strategies?




  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]