[
https://issues.apache.org/jira/browse/VELOCITY-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18034781#comment-18034781
]
Claude Brisson commented on VELOCITY-990:
-----------------------------------------
I think that the only correct solution would require a patch to the
maven-release-plugin (or a manual process meanwhile). It would consist in
having *two* concepts of tag: a tag used for an RC, 2.4.1-rc1, which is
effectively marked in the git tree, and a tag which is used as scm/tag in the
pom, 2.4.1, but *without* effectively declaring it as long as the vote is not
successful.
If the vote pass, then we add the final tag at the same point as the RC tag.
If the vote doesn't pass, the next RC will use another tag but the final tag
name is not burned out.
> 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]
