You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Peter Simon (JIRA)" <ji...@codehaus.org> on 2010/05/17 10:58:12 UTC

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

Check for changed subprojects (in multimodule projects) and release only the projects which have changed
--------------------------------------------------------------------------------------------------------

Key: MRELEASE-560
URL: http://jira.codehaus.org/browse/MRELEASE-560
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Affects Versions: 2.1
Environment: Windows Vista, jdk1.6.0_18
Reporter: Peter Simon
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 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