[ 
http://jira.codehaus.org/browse/MRELEASE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229474#action_229474
 ] 

Aaron Roller commented on MRELEASE-156:
---------------------------------------

I was able to use the scmCommentPrefix by following the instructions from this 
page:

http://jlorenzen.blogspot.com/2008/10/more-tips-on-using-maven2-release.html

Basically, I was getting denied by just providing the 
-DscmCommentPrefix=ABCD-1234 instead of providing -DscmCommentPrefix="JIRA: 
ABCD-1234 [maven-release-plugin]" 

> Prompt for customizing commit comment during release preparation
> ----------------------------------------------------------------
>
>                 Key: MRELEASE-156
>                 URL: http://jira.codehaus.org/browse/MRELEASE-156
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: prepare
>    Affects Versions: 2.0-beta-4
>            Reporter: Dário Oliveros
>
> Hi there,
> I've been trying to use maven-release-plugin to prepare a release, but 
> whenever I do that, it fails since I have a SVN precommit hook that 
> integrates with an issue tracking system  which in turn waits for a comment 
> containing an issue number. Since release plugin adds its own  comment, such 
> as  "[maven-release-plugin] prepare release ...", this integration fails. So 
> I was wondering if this could be prompted in the same way for the release and 
> next development iteration versions.
> Thanks,
> Dário

-- 
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


Reply via email to