On Mon, October 29, 2007 5:18 pm, maarten roosendaal wrote:
> I'm working with the maven-release-plugin and it works fine except for the
> fact that my own <module>-<version>-SNAPSHOT dependencies in various
> pom.xml's do no get updated when performing a release:prepare.
>
> I thought i could use the dependencyManagement for this but when i use
> this and do a release:prepare and start building, several modules will
> look for dependencies with the release version instead of the old SNAPSHOT
> version.
>
> What is the (best) way to avoid having to manually change all the
> versionumbers in de dependencies in the pom.xml's (we have 12) before
> performing a release?
If all 12 dependencies are typically released at the same time, then group
them together as a multi-module build and release the multi-module build
in one go.
We set the version in the root pom of our multi-module build, and in all
submodules, the version is inherited and accessed using ${pom.version}.
When the release:perform is run from the root of the multi-module build,
all the version numbers are handled automatically.
One thing that the release plugin likes to do when testing a multimodule
build is to miss out the install phase, which can cause potential
confusion as each of your submodules isn't installed and used by the next
submodule. To work around this problem, add this to your root pom:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-6</version>
<configuration>
<preparationGoals>clean install</preparationGoals>
</configuration>
</plugin>
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
