> In a multi-module situation it can of course happen that you have modules > which don't change between two or more releases.... > Is that a problem ? No it is not...
Well, it depends on your configuration management view on this. If I wear a CM hat, I think that the version of the API should not change if there is no change to the API. However, that would make your Maven projects setup slightly more complicated as you can't keep everything as one multi-module build. If you have a more relaxed view of this, you therefore release everything together (which is what most open source projects do). But, IMHO, that could confuse your users as a new version of an API suggests a change. /Anders > > The idea with multi-module builds to have a single point where you can > release a consistent state of your project... > > I'm using multi modules build very often and of course be faced with the > situation where only a small part of the project has been changed (only 1 or > 2 modules out of 10-15) ...but i will release them all....with a new version > (as mvn release will handle for me). > > Kind regards > Karl Heinz Marbaise > > ----- > Kind regards > Karl Heinz Marbaise > ---- > http://www.soebes.de > http://www.skmwiki.de > http://supose.org/wiki/supose > -- > View this message in context: > http://maven.40175.n5.nabble.com/Multi-modules-release-best-practices-tp5061771p5061858.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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
