[jira] [Resolved] (VELOCITY-990) Releasing: make sure that scm/tag in pom.xml matches git tag
"Claude Brisson (Jira)" <[email protected]> Wed, 22 Apr 2026 17:44:00 +0000 (UTC)
| Newsgroups | gmane.comp.jakarta.velocity.devel |
|---|---|
| Message-ID | <[email protected]> |
[ https://issues.apache.org/jira/browse/VELOCITY-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claude Brisson resolved VELOCITY-990.
-------------------------------------
Assignee: Claude Brisson
Resolution: Implemented
Added a {{release.sh}} script to engine
> 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
> Assignee: Claude Brisson
> 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)