You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2012/02/27 19:21:03 UTC
[jira] (MRELEASE-156) Prompt for customizing commit comment during
release preparation
[ https://jira.codehaus.org/browse/MRELEASE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292861#comment-292861 ]
Robert Scholte commented on MRELEASE-156:
-----------------------------------------
@Andrew, did you try it with {{ALT 10}} (=Line Feed) and/or {{ALT 13}} (=Carriage Return)?
The way Aaron is using the scmCommentPrefix is the preferred one.
By default we don't want to prompt for the comment prefix, so _if_ this feature is still need, you have to trigger it. By commandline is useless, since you can already pass it as an argument. As configuration-parameter seems like overkill to me. The only way I can think of is a more generic way, where you can define for which parameters you'd like to see a prompt. But that's a different feature request.
So I'm thinking of closing this as {{won't fix}}.
> 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
>
> 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