[
https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298209#comment-298209
]
Marcus Linke commented on MRELEASE-603:
---------------------------------------
This is our scenario here: We have a strongly modularized project with two
resulting deployment units (EARs) for our two different national branches.
There are a couple of base projects that both EARs depends on. The problem is,
that development is usually done by focusing on only one of the deployment
units and we can't release both EARs in parallel. So the consequence is that
the non-released EAR depends on older SNAPSHOTs which is OK but only until
releasing it. The 'versions-maven-plugin's 'use-latest-snapshots' goal
(http://mojo.codehaus.org/versions-maven-plugin/use-latest-snapshots-mojo.html)
should be executed as part of the release process to guarantee that the new
SNAPSHOT version depends on latest base project SNAPSHOT's itself.
> Allow configuration of goals to be executed after release creation
> ------------------------------------------------------------------
>
> Key: MRELEASE-603
> URL: https://jira.codehaus.org/browse/MRELEASE-603
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Reporter: Marcus Linke
> Assignee: Robert Scholte
> Priority: Minor
>
> It would be nice if the release plugin allows the configuration of some goals
> to be executed after the release creation. This could be used for example to
> configure the automatic execution of the maven-versions-plugin to update the
> dependencies versions of the newly created snaphot.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
