Return-Path: 
 <issues-return-2481-apmail-continuum-issues-archive=continuum.apache.org@continuum.apache.org>
Delivered-To: apmail-continuum-issues-archive@www.apache.org
Received: (qmail 90230 invoked from network); 4 Feb 2009 21:56:50 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 4 Feb 2009 21:56:50 -0000
Received: (qmail 23185 invoked by uid 500); 4 Feb 2009 21:56:50 -0000
Delivered-To: apmail-continuum-issues-archive@continuum.apache.org
Received: (qmail 23173 invoked by uid 500); 4 Feb 2009 21:56:50 -0000
Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@continuum.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@continuum.apache.org>
List-Post: <mailto:issues@continuum.apache.org>
List-Id: <issues.continuum.apache.org>
Reply-To: dev@continuum.apache.org
Delivered-To: mailing list issues@continuum.apache.org
Received: (qmail 23161 invoked by uid 99); 4 Feb 2009 21:56:50 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Feb 2009 13:56:50 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [63.246.2.115] (HELO codehaus01.managed.contegix.com)
 (63.246.2.115)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Feb 2009 21:56:42 +0000
Received: from codehaus01.managed.contegix.com (localhost.localdomain
 [127.0.0.1])
	by codehaus01.managed.contegix.com (Postfix) with ESMTP id BDB9B14A8169
	for <issues@continuum.apache.org>; Wed,  4 Feb 2009 15:56:19 -0600 (CST)
Message-ID: 
 <29349831.1233784579753.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Wed, 4 Feb 2009 15:56:19 -0600 (CST)
From: "Emmanuel Venisse (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [jira] Closed: (CONTINUUM-2028) Continuum release prepare should
 use maven-release-plugin scmCommentPrefix configuration in pom
In-Reply-To: 
 <33244799.1230677719764.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 4e90ceb663894a42f12c0e28abbab431
X-Virus-Checked: Checked by ClamAV on apache.org


     [ http://jira.codehaus.org/browse/CONTINUUM-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse closed CONTINUUM-2028.
---------------------------------------

      Assignee: Emmanuel Venisse
    Resolution: Fixed

Done in r.740906

> Continuum release prepare should use maven-release-plugin scmCommentPrefix configuration in pom
> -----------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2028
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2028
>             Project: Continuum
>          Issue Type: Improvement
>    Affects Versions: 1.2.2
>         Environment: Continuum 1.2.2, Subversion
>            Reporter: Wendy Smoak
>            Assignee: Emmanuel Venisse
>             Fix For: 1.3.2
>
>
> I have a Subversion repository with a pre-commit hook that requires a valid issue tracker id in every commit message.
> The default commit message for release prepare is "[maven-release-manager] prepare for next development iteration" which is not acceptable.
> I tried configuring the scmCommentPrefix for the release plugin in the pom, but the commit message still came out as  [maven-release-manager] and was rejected.
> {noformat}
>   <build>
>     <plugins>
>       <plugin>
>         <artifactId>maven-release-plugin</artifactId>
>         <configuration>
>           <scmCommentPrefix>[ABCD1234]</scmCommentPrefix>
>         </configuration>
>       </plugin>
>     </plugins>
>   </build>
> {noformat}

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