Now that maven-release-plugin-2.0-beta-6 has been released (I think it has, though I don't recall an announcement), I would like to get this patch applied or at least generate some discussion on the issue.
http://jira.codehaus.org/browse/MRELEASE-235 I intend to open-source my plugin that relies on this behaviour, but can't do so until the behaviour actually exists in the release-plugin. I would rather bind my plugin to a particular release phase and just have it execute at that time, than have to force its execution b7y directly executing its goals from the release-plugin as also happens for the RunPerformGoals and RunPrepareGoals phases. Wouldn't it be better to make the phases of the release-plugin part of a release life-cycle sames as the clean, site and standard lifecyles? And allow people to bind their plugins to those phases? I would still need a RunPostPrepareGoals phase, but at least the wiring of my plugin to that phase would seem more natural and follow a standard maven pattern. William --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
