[
https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298685#comment-298685
]
Robert Scholte commented on MRELEASE-603:
-----------------------------------------
The {{perform}}-goal is about checking out the project by the release-tag and
run several release-goals on that projects, usualy {{deploy}} and
{{deploy-site}}.
Your goal is to have the pom.xml ready for the next development-cycle, which
should be part of the {{prepare}}-goal.
I think that a post-perform goal wouldn't help.
Correct me if I'm wrong, but this is how I read your story:
In this order the projects have been released:
* shared-1
* earA-1 (using shared-1)
* earB-1 (using shared-1)
* shared-2
* earA-2 (using shared-2)
* earA-3 (using shared-2)
* shared-3
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.
So it seems like you've developed with the wrong snapshot version, and no
post-goal would have helped here.
I'd prefer not to use a fully automated call of {{use-latest-version}}, but
that's something a CI-system could do for you. Also think of the checkin, which
has to follow.
> 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
