Hi,
Change was reverted from maven-parent
https://github.com/apache/maven-parent/pull/468
On Thu, 1 May 2025 at 22:30, 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://git
Personally I am opposed to changing the default to a worse format and
introduce a breaking change.
The `v` is redundant. If users want to use that we should enable a
configuration to do so (I think that exists already) but the default
should stay as is and use the project version.
On 2025-05
atum: Freitag, 2. Mai 2025 um 09:57
> An: 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
>
>
-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.ve
Explanation: I am talking about some automation that for example uses
JGit to get version information and so on... so "sorting on GH UI" is
one thing, but automatic processing of tags by various means is
completely different.
T
On Thu, May 1, 2025 at 10:37 PM Tamás Cservenák wrote:
>
> Howdy,
>
Howdy,
I don't see why we want to change tag format (!) on existing,
especially long time existing and running projects.
What gain does it give ASIDE for some tooling nicer output, that we
never used before (that generates something out of it)?
How to sort history after? How to process tags for so
