[jira] Closed: (MRELEASE-160) The next snapshot version is not used un submodules

["Emmanuel Venisse (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MRELEASE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse closed MRELEASE-160.
-------------------------------------

         Assignee: Emmanuel Venisse
       Resolution: Fixed
    Fix Version/s: 2.0-beta-5

Already fixed.

> The next snapshot version is not used un submodules
> ---------------------------------------------------
>
>                 Key: MRELEASE-160
>                 URL: http://jira.codehaus.org/browse/MRELEASE-160
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-4
>            Reporter: Joerg Schaible
>            Assignee: Emmanuel Venisse
>             Fix For: 2.0-beta-5
>
>         Attachments: 2.0-beta-4.patch, dryRun.patch, PomRewriteVersions.patch
>
>
> In multi-module mode the release plugin replaces the version of snapshot dependencies in the submodules automatically for dependencies that are also part of the release. But this versions are not set to the next version after the release process. E.g. in a module with two submodules (one EJB and an EAR depedning on this EJB) the EJB depednency is added with a SNAPSHOT depednecny. At release time the plugin replaces this version with the version used for the release. After the release the version tag in the parent section of both POMs are set to the next version, but the verison in the EARs depednency stays at the release. This is higly error-prone, since with the next release the EAR still references the old version of the EJB.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira