Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: 
 <15492537.1234505300494.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Fri, 13 Feb 2009 00:08:20 -0600 (CST)
From: "Emmanuel Venisse (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [jira] Updated: (CONTINUUM-1503) scm release tag default should
 match what the release plugin uses
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Emmanuel Venisse updated CONTINUUM-1503:
----------------------------------------

         Assignee: Emmanuel Venisse
    Fix Version/s:     (was: 1.x)
                   1.3.2

> scm release tag default should match what the release plugin uses
> -----------------------------------------------------------------
>
>                 Key: CONTINUUM-1503
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1503
>             Project: Continuum
>          Issue Type: Bug
>          Components: Release
>    Affects Versions: 1.1-beta-3
>            Reporter: Tomislav Stojcevich
>            Assignee: Emmanuel Venisse
>             Fix For: 1.3.2
>
>
> The release plugin gives a default scm tag to used when doing a release:prepare, continuum's release prepare does not use the same value.
> I happen to be on a branch so in continuum my project's scm tag is the branch name. (using cvs).
> When i went to release prepare, the tag default was the existing value in the pom for the scm tag.  I didn't change it and when the project finished the prepare, there was nothing tagged (because the tag it tried to use was the same name as the branch I was on).
> The release plugin uses a different default and doesn't create this problem.

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