We were almost in same situation and after deeply analyzing projects such as Jetty, Camel etc. concluded that the best practice for us releasing all of the modules at one time even if some projects haven't changed. At first it seems that there is nothing changed but it has very crucial side effects. Tests. Each release should increase the safety level of the library despite of unchanging. The key point here is correct classification. If you feel that all of your libraries are tightly coupled to each other, I feel that you are in the correct way to release all of them at one time. However separating API modules to another project seems more reasonable for me in order to prevent confusion for your users.
-- View this message in context: http://maven.40175.n5.nabble.com/Multi-modules-release-best-practices-tp5061771p5070889.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
