maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Poisson (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MRELEASE-967) scmCommentPrefix is not used when tagging
Date Mon, 13 Feb 2017 13:52:41 GMT

    [ https://issues.apache.org/jira/browse/MRELEASE-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863694#comment-15863694
] 

Nicolas Poisson edited comment on MRELEASE-967 at 2/13/17 1:52 PM:
-------------------------------------------------------------------

Attached is a zip containing the sample project. URLs for the various systems have been obfuscated
but you can plug in your own. 

Please note that I have tried several versions of the scmCommentPrefix, with issue number
hard-coded in the string, with trailing spaces (which unfortunately get trimmed) so it doesn't
get jammed against the rest of the mrp comment, etc. but they all have the same effect.

Also please note that I am able to create the tag on local, but simply cannot push it to the
remote repo.

Also, the 1.9.5 versions of the dependencies are not mandatory, you get the behavior anyway
but I was trying to fix the issue of password appearing in clear text in logs upon fatal error.



was (Author: poin027):
Attached is a zip containing the sample project. URLs for the various systems have been obfuscated
but you can plug in your own. 

Please note that I have tried several versions of the scmCommentPrefix, with issue number
hard-coded in the string, with trailing spaces (which unfortunately get trimmed) so it doesn't
get jammed against the rest of the mrp comment, etc. but they all have the same effect.

Also please note that I am able to create the tag on local, but simply cannot push it to the
remote repo.


> scmCommentPrefix is not used when tagging
> -----------------------------------------
>
>                 Key: MRELEASE-967
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-967
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.5.3
>         Environment: Linux, Maven 3.3.9, jdk 1.0.8_102, GIT
>            Reporter: Claus Nielsen
>         Attachments: mrp-git-jenkins.txt, mrp-git-local.txt, mrp-test.zip
>
>
> We use a Jira Hook in out GIT installation to ensure a Jira Ticket in all commits. This
is of course also activated when the release plugin comes into play.
> When using release prepare with the scmCommentPrefix parameter, the commit message is
not as expected when it comes to tagging. The initial prepare commit where the release version
is committed works fine with the scmCommentPrefix, but in the next phase where the actual
tagging is made the value in scmCommentPrefix is ignored. This result in a failing release
with a lot of manual cleaning up in poms... :-(
> I can see that there was a problem with this earlier before using scm api 1.3 and before
the maven release version 2.0. But this should be fixed now.
> Here is an example:
> mvn release:prepare release:perform '-DscmCommentPrefix=NIS-145 NIS-295 (clausfod)' -Dresume=false
'-Darguments=-DskipTests'



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message