[
https://issues.apache.org/jira/browse/SCM-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961853#comment-17961853
]
ASF GitHub Bot commented on SCM-509:
------------------------------------
jira-importer opened a new issue, #723:
URL: https://github.com/apache/maven-scm/issues/723
**[Robert
Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)**
opened
**[SCM-509](https://issues.apache.org/jira/browse/SCM-509?redirect=false)** and
commented
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
* http://fisheye.codehaus.org/changelog/qdox/?cs=664
* http://fisheye.codehaus.org/changelog/qdox/?cs=665
* http://fisheye.codehaus.org/changelog/qdox/?cs=666
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 message.
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.
---
**Affects:** 1.2
> Tagging fails to use provided message while checking in works fine
> ------------------------------------------------------------------
>
> Key: SCM-509
> URL: https://issues.apache.org/jira/browse/SCM-509
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-api
> Affects Versions: 1.2
> Reporter: Robert Scholte
> Priority: Critical
>
> 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
> * http://fisheye.codehaus.org/changelog/qdox/?cs=664
> * http://fisheye.codehaus.org/changelog/qdox/?cs=665
> * http://fisheye.codehaus.org/changelog/qdox/?cs=666
> 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 message.
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
