[
https://issues.apache.org/jira/browse/VELOCITY-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18034783#comment-18034783
]
Claude Brisson commented on VELOCITY-990:
-----------------------------------------
Others are hitting this problem as well. See the [Apache Commons release
process|https://commons.apache.org/releases/prepare.html] : they have a manual
process and special instructions to avoid this problem with the maven release
plugin.
> 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
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
