Hi,
Max Carpentier wrote > > We would like to make a new release of the project, but there's a problem > : project-external-api and and project-ws-api haven't changed since the > last release... > what should we do ? > Very short answer: So what? Just make the release and it's done. Is it a problem in your version control to tag a directory structure ? Max Carpentier wrote > > ... > any other idea ? > What are the best practices for this kind of situation ? have we missed > something in maven multi modules setup ? > 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... 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]
