the goal is only intended for versioning, tagging, and releasing a single project. So if you wish to version and release your subprojects individually, you should run it once each - but if this is your requirements you should probably be developing each individually.
If you only want one version and tag for all your subprojects and release them together, you should run it from the parent project. As long as all the subprojects are subdirectories, the tagging will apply to all. If you put the version in the parent POM and inherit it, then that will apply to all. I prefer to develop in the first manner and have each milestone its own scope and roadmap. - Brett On Fri, 10 Sep 2004 09:18:32 +0200, Nicolas De Loof <[EMAIL PROTECTED]> wrote: > > Hi all, > > I'm trying to setup a release of my app. > It uses multiples sub-projects and maven multiproject to build. > > Now I'd like to tag version and want to use scm:prepare-release goal > It requires me to lauch maven on each sub-projects according to dependencies between > them and update POMs that depends > on it to reflect the updated version number. > > Do you have any best practice / suggestion about it ? > > Nico. > > This message contains information that may be privileged or confidential and is the > property of the Capgemini Group. It is intended only for the person to whom it is > addressed. If you are not the intended recipient, you are not authorized to read, > print, retain, copy, disseminate, distribute, or use this message or any part > thereof. If you receive this message in error, please notify the sender immediately > and delete all copies of this message. > > --------------------------------------------------------------------- > 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]
