Tobias Gierke wrote: > You got the spelling wrong, it's "-DdryRun". See > http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html >
Thanks, got it. >> - How can I exclude modules from being versioned/tagged? >> >> > You don't. You need to group your projects by release cycles - only > projects that share a common release cycle should be placed under the > same parent (at least that's what I always do). > >> - The scm-element is ignored in the submodule. In either variant testA >> is not tagged in subversion, in variant B) the externals point to >> trunk/testA (absolute path) or to tags/testA (relative path, not existent). >> >> > Since those projects should share the same release cycle , tagging > individual sub-projects separately makes no sense (they all share the > same version number anyway) Afaik, that's not correct (rather bold for a newbie, isn't he ;-) The sub-projects only share the same version number if you set autoVersionSubmodules=true. Btw, keeping things modular means that modules may be used in several projects. It's important for our business to keep the different module-sets versioned, so if one module is tagged/versioned the whole set is tagged. It doesn't make sense to me to tag every module when changing only one because it implies that every module has been changed. Sorry for the project/module naming mess. Regards, Florian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
