[
https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298728#comment-298728
]
Marcus Linke commented on MRELEASE-603:
---------------------------------------
{quote}
Now we want to release earB-2, which probably depends on shared-2-SNAPSHOT (not
the latest snapshot) since earB-1 was released before shared-2.
You probably want this release to use shared-3.
{quote}
This is exactly the problem. We don't want the release of earB-2 use shared-3
but shared-2 as the CI builds for earB depends on shared-2-SNAPSHOT at this
time and we can't guarantee that shared-3 is compatible with shared-2-SNAPSHOT
anymore.
After the release of earB the new earB-3-SNAPSHOT should depend on
shared-4-SNAPSHOT so the CI system will show us incompatibilities with the new
shared component and developers are invited to fix this. All this could be
achived by hooking in {{versions-maven-plugin:use-latest-version}} into the
(post-)release process. The {{versions-maven-plugin:use-latest-version}} goal
is highly configurable and would allow us to exclude and include specific
artifacts per project.
The checkin to SCM could be done manually by the release maintainer but could
be configured via the new post-perform goals option too.
> 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
