maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] Closed: (SCM-509) Tagging fails to use provided message while checking in works fine
Date Tue, 17 Nov 2009 20:13:55 GMT


Robert Scholte closed SCM-509.

       Resolution: Duplicate
    Fix Version/s: 1.3

Hmm, this explains it SCM-460

> Tagging fails to use provided message while checking in works fine
> ------------------------------------------------------------------
>                 Key: SCM-509
>                 URL:
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-api
>    Affects Versions: 1.2
>            Reporter: Robert Scholte
>            Priority: Critical
>             Fix For: 1.3
> During a mvn prepare:release there are 3 scm-action: checking in release pom, tagging,
checking in pom for next snapshot. Both the checkins have a message starting with [maven-release-plugin],
while the tag the the default message [maven-scm]
> After some investigation it seems like it works like this for ages although according
to the code the attempt is to give them all the same prefix.
> Compare these changelogs for example
> *
> *
> *
> For me it's critical, because with a current project our SVN system has a prehook which
requires every message to start with BugID: {theId}. 
> I thought I found it, but cheered a bit too early.
> The {{org.apache.maven.scm.command.tag.AbstractTagCommand}} is responsible for the default
> It seems like {{parameters.getScmTagParameters( CommandParameter.SCM_TAG_PARAMETERS );}}
was empty, so it returned an empty {{ScmTagParameter}}
> These params were created at {{org.apache.maven.shared.release.phase.ScmTagPhase}}  and
{{org.apache.maven.scm.provider.AbstractScmProvider}} adds them to the CommandParameters.

> Somewhere around here something goes wrong.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message