Thanks for suggestion! I found my problem: shouldn't use a variable like "project.release.version". Maven must try to look that value under <project> node. When I replace with a uncommon name like "fancyBuild.version", then everything works as expected.
On Fri, May 16, 2008 at 1:12 PM, Clifton <[EMAIL PROTECTED]> wrote: > > You want to use the release plugin with a multi module project. Setup a > super > pom with packaging = pom and artifactId set to whatever (eg. artifactId: > MyProj) and include projects A and B as sub modules. When your ready to cut > a release just run > mvn release:prepare release:perform > on the cmd line and the plugin takes care of all your dirty work, > incrementing your version numbers automatically creating tags in VCS > resolving the pom including the version of everything involved in the build > checking in the resolved pom and more. Read the "Better Builds With Maven" > PDF freely available on line to get more detail about the release plugin. > Trust me, using anything less will only complicate your project management. > >
