Hallo, Marshall.
By flat hierarchy do you mean that the aggregator project directory is
not the parent directory of your modules' directories, but resides side
by side with them? If so, this may be your problem. I believe that the
release plugin expects the modules to reside in subdirectories of the
aggregator's directory.
Moreover this is to be the case even within your version control system,
i.e. Subversion externals or similar mechanisms are not handled properly.
Cheers,
Nicola Musatti
Marshall Schor wrote:
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]
Chi riceve il presente messaggio e' tenuto a verificare se lo stesso non gli
sia pervenuto per errore. In tal caso e' pregato di avvisare immediatamente
il mittente e, tenuto conto delle responsabilita' connesse all'indebito
utilizzo e/o divulgazione del messaggio e/o delle informazioni in esso
contenute, voglia cancellare l'originale e distruggere le varie copie o
stampe.
The receiver of this message is required to check if he/she has received it
erroneously. If so, the receiver is requested to immediately inform the
sender and - in consideration of the responsibilities arising from undue use
and/or disclosure of the message and/or the information contained therein -
destroy the original message and any copy or printout thereof.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
