Did you try using ${project.version} in the dependency management section ?


On 4/29/10, Kaiser, Nils <[email protected]> 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:
>
> <project ...
> ...
>                 <groupId>...</groupId>
>                 <artifactId>notif-platform</artifactId>
>                 <packaging>pom</packaging>
>                 <version>1.3.1-SNAPSHOT</version>
> ...
>                 <modules>
>                                <module>core-model</module>
>                                <module>core-persistence</module>
>                                <module>core-datasource</module>
>                                <module>core-webapp</module>
>                                <module>notif-core</module>
>                                <module>notif-model</module>
> ...
>                 </modules>
>
>                 <dependencyManagement>
>                                <dependencies>
>                                                <dependency>
>
> <groupId>de.adesso.mobile.devicebackend</groupId>
>
> <artifactId>notif-core</artifactId>
>
> <version>1.3.1-SNAPSHOT</version>
>                                                </dependency>
>                                                <dependency>
>
> <groupId>de.adesso.mobile.devicebackend</groupId>
>
> <artifactId>notif-model</artifactId>
>
> <version>1.3.1-SNAPSHOT</version>
>                                                </dependency>
>                                                <dependency>
>
> <groupId>de.adesso.mobile.devicebackend</groupId>
>
> <artifactId>notif-persistence</artifactId>
>
> <version>1.3.1-SNAPSHOT</version>
>                                                </dependency>
> ...
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to