[jira] [Updated] (MRELEASE-560) Check for changed subprojects (in multimodule projects) and release only the projects which have changed

["Elliotte Rusty Harold (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MRELEASE-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold updated MRELEASE-560:
-------------------------------------------
    Issue Type: New Feature  (was: Improvement)

> Check for changed subprojects (in multimodule projects) and release only the projects which have changed
> --------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-560
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-560
>             Project: Maven Release Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.1
>         Environment: Windows Vista, jdk1.6.0_18
>            Reporter: Peter Simon
>            Priority: Major
>         Attachments: releaseOnlyChangedProjects.patch
>
>
> This feature makes it possible for multimodule projects to configure if the subprojects that have no changes since the last release shell be released or not. By setting the argument -DreleaseOnlyChanged=true only the changed submodules will be released (default -DreleaseOnlyChanged=false).
> To compare the workingcopy with the last release, the poms are modified by adding a property lastReleaseRev which contains the revision of the last release. If this property doesn't exist (as it is for the first release) the project will be released.
> If only the changed subprojects shall be released, the different phases (f.ex. RewritePomsPhase) will be skipped for those projects.
> This patch also includes the patch for MRELEASE-550.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)