Maybe some side-angle from a fellow Apache project In PLC4X we build all of our variants with maven ... also PLC4Go. When releasing we changed tagging of releases to use the „v-notation“ as this allows simpler integration into the Go dependency resolution.
However I would not say that this use-case is so standard, that it should be part of the apache parent. Just wanted to add some info on where it might be useful. Chris Von: Michael Osipov <micha...@apache.org> Datum: Freitag, 2. Mai 2025 um 09:57 An: dev@maven.apache.org <dev@maven.apache.org> Betreff: Re: Release tag format for Maven projects -1 The 'v' is absolutely redundant since it does repeat on every object. See also: https://github.com/apache/maven-release/pull/122 On 2025/05/01 20:30:02 Slawomir Jaranowski wrote: > Hi, > > We introduce a short and the same template release tag name for Maven > projects as: > > v@{project.version} > > in parent 44: https://github.com/apache/maven-parent/pull/455 > > It will change a tag name on history ... but for me is more modern and > simplified other configurations like for release-drafter > > It is also used in GitHub to point release notes, eg > > old tga format > https://github.com/apache/maven-clean-plugin/releases/tag/maven-clean-plugin-3.4.1 > > new tag format: > https://github.com/apache/maven-parent/releases/tag/v44 > > so we don't have a duplicate component name in the path. > > > Any objections for the new tag format ...? > > -- > Sławomir Jaranowski > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
