[
http://jira.codehaus.org/browse/MRELEASE-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104167
]
Quinten Verheyen commented on MRELEASE-214:
-------------------------------------------
Yes, I can conform this bug is re-introduced or not fixed, it still occurs in
2.0-beta-7.
The file used in the svn tagging contains the default prefix, not the specified
one.
I checked this and the generated release.properties file does not contain the
"scm.commentPrefix" property either. Despite it being provided as a parameter :
tried it in 2 ways, via -DscmCommentPrefix and via the <configuration> node in
the pom.
I think for some reason config.getScmCommentPrefix() = null, hence it explains
why it's not writtend in the properties file and the default prefix is used.
> scm:tag with scmCommentPrefix
> -----------------------------
>
> Key: MRELEASE-214
> URL: http://jira.codehaus.org/browse/MRELEASE-214
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.0-beta-5
> Environment: macosx
> Reporter: fabio melen
> Assignee: Emmanuel Venisse
> Fix For: 2.0-beta-5
>
>
> My svn repository use a pre-commit hook in order to check the commit message
> and to validate it (Trac integration). So I'd like that the scm:tag, invoked
> from release:prepare, inherits the scmCommentPrefix value.
> ciao
> fabio
--
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
