[ http://jira.codehaus.org/browse/MRELEASE-160?page=comments#action_79350 ] Joerg Schaible commented on MRELEASE-160: -----------------------------------------
Hi Tom, I am not talking of the dryRun. The described behavior applies to the real release process. - Jörg > 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 > > 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
