[
https://jira.codehaus.org/browse/MRELEASE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-185.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
Assignee, if you think you can fix this bug anytime soon, please reopen and
proceed appropriately.
> Regardless of what profile is used for releasing the release information in
> the metadata needs to be updated
> ------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-185
> URL: https://jira.codehaus.org/browse/MRELEASE-185
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.0-beta-4
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
>
> Right now with the release profile buried in the Super POM you have to make
> sure that you configure the deploy plugin to update the release info. A user
> would probably assume that any profile used would also be accompanied by the
> release information being updated.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
