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

Przemyslaw Wojnowski commented on MRELEASE-156:
-----------------------------------------------

Could you add an example to the FAQ?

I've such configuration:
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-release-plugin</artifactId>
  <version>2.3.2</version>
    <configuration>
      <scmCommentPrefix>ABCD-1234 ALT 10</scmCommentPrefix>
    </configuration>
</plugin>

And when I issue "mvn release:prepare -DdryRun=true" it doesn't show any new 
line:
[INFO] Full run would be commit 4 files with message: 'ABCD-1234 ALT 10prepare 
release my-project-1.0.1'
                
> Prompt for customizing commit comment during release preparation
> ----------------------------------------------------------------
>
>                 Key: MRELEASE-156
>                 URL: https://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
>            Assignee: Robert Scholte
>
> 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, 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


Reply via email to