[jira] [Commented] (VELOCITY-990) Releasing: make sure that scm/tag in pom.xml matches git tag

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

Nathan Bubna commented on VELOCITY-990:
---------------------------------------

As usual, in software or really any system with non-trivial complexity, the question is never *whether* there will be something annoying (leaky abstractions, hassle, confusion, whatever) but instead *where/which* annoyance will be.

Given that presupposition, i therefore regularly lean toward the conservative path of keeping the annoyance right where it has always been. You know, a preference for the devil you know over the unknown.

Translation: I'm with Claude on this, despite being sympathetic to the Maven-ish arguments.

> Releasing: make sure that scm/tag in pom.xml matches git tag
> ------------------------------------------------------------
>
>                 Key: VELOCITY-990
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-990
>             Project: Velocity
>          Issue Type: Task
>            Reporter: Peter Palaga
>            Priority: Major
>         Attachments: release.sh
>
>
> Hi, I noticed the following issue on recent releases that were preceded by RCs: 
> The scm/tag is the RC version, not the actually released version that is present in <version> and that would match git tag.
> For example, for release 2.4.1, the tag and versions in pom.xml files are all {{2.4.1}}, but the scm/tag is 
> {code:xml}
>     <scm>
>         ...
>         <tag>2.4.1-rc1</tag>
>     </scm>
> {code}
> Could you please adjust your processes next time, to make rebuilds easier? 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)