Hi, I have a multi-module project, using a *flat* hierarchy.
The top pom I'm running the mvn release:prepare -DdryRun=ture command has a <modules> section which specifies the submodules. The top pom and all the poms in the submodules have version numbers 2.3.1-SNAPSHOT. The top pom has *some* of the submodules also listed as <dependencies>, with the 2.3.1-SNAPSHOT version. When I run the release:prepare goal, it asks me if I want to "resolve" snapshots, just for those listed in <dependencies>. I say yes, and select 1:Project Dependencies at the next prompt. For all dependencies listed in <dependencies> it then asks if I want to "set to release*; I say yes, and also take the default for the "next" version. Then it's off and running, and after a while says "BUILD SUCCESS". It appears to have prepared poms for the top pom that reflect updating for the release version, OK (the release version of the pom is 2.3.1, without the -SNAPSHOT, etc.). But it did not change any poms for the projects built underneath (the ones in the <modules> section). Also, a submodule's "target/xxx.pom" shows the -SNAPSHOT version still. Perhaps I have a mistaken idea hear. I thought that if my multi-module project had <module> parts with a -SNAPSHOT version, that "releasing" the top-pom would result in *all* of the modules getting their version updated. What is the right way to get all these modules released, in one go, with their versions switched from -SNAPSHOT to the release version? (Tried using release plugin version 2.0, trying both maven 3.0-beta-1 and 3.0-RC2 - same results.) -Marshall Schor --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
