[ http://jira.codehaus.org/browse/MRELEASE-160?page=all ]

Tom Parker updated MRELEASE-160:
--------------------------------

    Attachment: dryRun.patch

Fixes behaviour of dryRun.

The real thing does this:
translate pom.xml to pom.xml in rewrite-poms-for-release phase
commit pom.xml
translate pom.xml to pom.xml in rewrite-poms-for-development phase
commit pom.xml

The dryRun does this:
translate pom.xml to pom.xml.tag in rewrite-poms-for-release phase
translate pom.xml to pom.xml.next in rewrite-poms-for-development phase

Note that in the rewrite-poms-for-development phase, the real thing translates 
the tagged pom.xml while the dryRun translates the original pom.xml.

This patch makes dry run rewrite-poms-for-development phase read pom.xml.tag 
created by the rewrite-poms-for-release phase as it's input.

> 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
>         Attachments: dryRun.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

        

Reply via email to