Did you try using ${project.version} in the dependency management section ?
On 4/29/10, Kaiser, Nils wrote:
> Hello,
>
> In our multi-module project we included the module dependencies in the
> dependencyManagement of the parent POM to be able to leave out versions in
> the module POMs. Here a snippet extracted from the master POM:
>
> ...
> ...
> notif-platform
> pom
> 1.3.1-SNAPSHOT
> ...
>
>core-model
>core-persistence
>core-datasource
>core-webapp
>notif-core
>notif-model
> ...
>
>
>
>
>
>
> de.adesso.mobile.devicebackend
>
> notif-core
>
> 1.3.1-SNAPSHOT
>
>
>
> de.adesso.mobile.devicebackend
>
> notif-model
>
> 1.3.1-SNAPSHOT
>
>
>
> de.adesso.mobile.devicebackend
>
> notif-persistence
>
> 1.3.1-SNAPSHOT
>
> ...
>
> We used continuum and the release plugin to manage the releases. In the
> past, the release plugin had no problems with updating the versions in the
> dependenyManagement of the parent POM.
>
> However, since version 2.0 (beta8 is automatically used, but 2.0 shows the
> same behavior) the release plugin does not change the versions in the
> dependencyManagement of the parent POM anymore. It thus produces a "broken"
> project after running the release plugin, as the module versions are changed
> in the respective module POMs, but not in the dependencyManagement of the
> master POM.
>
> Is it an error in the new release plugin version?
>
> Is use of module dependency versions in dependencyManagement of the POM
> discouraged now?
>
> Should I submit an issue?
>
> Best regards,
>
> Nils Kaiser
>
--
Sent from my mobile device
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
