[
http://jira.codehaus.org/browse/MRELEASE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Ferguson closed MRELEASE-213.
-------------------------------------
Resolution: Won't Fix
I got around this issue by retrieving the information from Subversion directly.
But this has meant that the plugin which does so needs to be executed as a
precise point in the release which is NOT the prepareGoals phase - which makes
http://jira.codehaus.org/browse/MRELEASE-213 all the more important.
> Need ability to access values gathered by maven-release-plugin in Mojos
> executed as part of preparationGoals element
> --------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-213
> URL: http://jira.codehaus.org/browse/MRELEASE-213
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-4
> Reporter: William Ferguson
>
> I have a plugin containing a Mojo that needs to be executed as part of the
> maven-release-plugin's preparationGoals phase.
> The Mojo needs access to some of the information gathered by the
> maven-release-plugin.
> Namely it needs access to the SCM release tag specified by the user.
> The aim of the plugin is to update the subclipse:tags property of the project
> being released in a similar manner that the Eclipse/Subversion Subclipse
> plugin does. So the information that I need to gather from the
> maven-release-plugin is
> 1) SCM release tag specified by the user.
> 2) Any other SCM details that have been modified for the release plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
